Buy

MCP

Free & Premium

The MCP window (⌘7) shows the MCP servers on your Mac: which ones are running right now, who owns them and what is configured in which client. MCP (Model Context Protocol) is the standard AI clients such as Claude Code, Cursor or Codex use to plug in extra tools. An MCP server provides such tools, for example access to GitHub, a database or the browser. The window is the same view as the MCP page in WebDonkey, and it also works when WebDonkey is not installed.

What you do here

  • See which servers are running and stop the ones that got stuck: Running.
  • Look at what is configured in your clients, check a server, add, edit, turn on and off, copy or remove entries: Configured.
  • Find out why a server is missing and add clients the editor does not know yet: Clients.

Layout of the window

Area What is there
Header The totals, for example "3 running · 12 configured · 1 orphaned". Orphaned only shows up when there are orphaned servers. On the right three icon buttons, their names are in the tooltip: Refresh, Clean up orphans (only when there are orphans) and Add server. On Free, Add server also shows how many free servers are used, for example 1/2.
Tabs Running, Configured and Clients, each with its count.
Filter line On Running and Configured: chips per client (All and one chip per client, as soon as more than one client has entries), the search field Search MCP servers…, a select All projects or one project, and the chips This project and Everything.
List The servers in groups. Clicking a row unfolds its details. With more than 300 rows the groups start folded.
Notices After every change a notice at the top says what was written and what the client has to do now. After a write there is Undo.

This project is the default. On Running it means: the servers of the sessions running in your project folder, and the IDE bridge of this editor window. On Configured it means: the entries of this project plus every entry that applies to you as a user everywhere. Everything shows all projects. When nothing matches, the list says "Nothing matches the filter." with Clear filter.

What the editor adds

The view is WebDonkey's, the editor connects it to its window:

  • Open file, and Open as tab for logs, open the file as a tab in the editor area, for entries right at the entry's line.
  • Run in terminal runs a command, a login for example, in the editor's terminal. If you hid the terminal under Settings › Features, the window shows the command for you to copy instead.
  • The IDE bridge of this window (Claude Code talks to the editor through it, see The IDE bridge) carries the label this window.
  • If you detached the MCP window into a window of its own, files and terminals go to the project window it belongs to.

How fresh the list is

The window reads again every 3 seconds while it is visible and the editor is in front, every 15 seconds while the editor is in the background, and not at all while the window is hidden. Refresh reads right away. If reading fails, it says "The last refresh failed. Showing the state of …" with the time.

Free and Premium

Free Premium
See every running and configured server, in every client The lists of tools, resources and prompts when checking, plus the server's instructions and its error output
Stop single servers Clean up orphans in one go
Check and Check through … A server's Logs
Show configuration, Open file, Copy command Add more than 2 servers, write to several clients at once
Remove and Log in Edit, Turn on and Turn off, Copy to other clients
Add up to 2 servers Reset approvals (Claude Code), add and edit your own clients

What counts are the servers you added through WebDonkey or the editor that still exist. Remove one and its place is free again. Locked buttons carry the Premium mark, clicking one opens the Premium page in your browser. Premium applies when WebDonkey Premium is active, either through WebDonkey or through the license key you entered in the editor. Prices are on webdonkey.io/pricing.

If you don't need the window, hide it under Settings › Features › Tool windows. A hidden window is not loaded.

Running Free & Premium

The Running tab lists the MCP servers that are running as a process on your Mac right now. A server usually starts with its client, a Claude Code session for example, and shows up here for as long as it runs. You see who started it and how much memory it uses, and you stop servers that were left behind.

Where to find it

Open the MCP window with ⌘7 or its icon in the right stripe and pick the Running tab. When nothing runs, it says: "No MCP server is running right now."

What the list shows

The servers are grouped by owner:

Group Meaning
Client and session One group per client process, for example "Claude Code · shop". Next to it the uptime (for …), the project folder and the app the client runs in ("in iTerm2").
Started by hand Servers someone started in a terminal.
Service Servers running as a service.
Check in progress Copies started for a check right now.
Orphaned "their client is gone, they kept running": the client quit, the server did not.

Every row shows the name, the type (stdio, HTTP, SSE, WebSocket or IDE bridge), the command or address, and on the right PID, port, uptime, memory and CPU load. Orphaned servers have an orange edge, the others a green one. Labels mark anything unusual:

Label Meaning
this window The IDE bridge of this editor window.
not in a configuration Recognised by its command, not listed in any configuration file.
Docker Runs through Docker. Only Docker's client process is visible, the usage does not include the container.
duplicate A second copy of the same configuration under the same client.
port open The port is open. Only a check tells whether an MCP server answers there.
lock without process The lock file is still there, the process is not.
other user Belongs to another user of this Mac.

Details of a row

Click a row to unfold its details:

  • Command or URL: in full.
  • Process: PID, number of processes, uptime, memory and CPU.
  • Owner: client, session, project folder, app and the client's PID.
  • Matched by: Matched to a configuration, Recognised by its command or Announced by the app (lock file). Clicking the named entry takes you to it in Configured. If the process fits several entries, "Also matches: …" follows.
  • Notes: what the labels mean in detail.
  • Cannot be stopped: the reason, if the server cannot be stopped from here.

The ⋯ menu of a row holds Logs (when the client writes logs, Premium), Show configuration (jumps to the entry in Configured, unfolds it and highlights it for a moment) and Copy command.

Stop a server

  1. Click Stop (the square) in the row.
  2. The dialog "Stop “name”?" says what happens. For Claude Code: "Claude Code loses the tools of this server until you choose /mcp → Reconnect there." Other clients may start the server again right away. Below that are warnings, for example when the server is busy (CPU above 5 %) or runs through Docker or launchd, plus the command and PID.
  3. Click Stop. The server is asked to quit.
  4. If it does not react, the dialog says so and lists the PIDs still running. Stop now ends them hard (SIGKILL). That never happens by itself.

Not every process can be stopped. The reason is shown, for example: it is WebDonkey itself or a client, the process belongs to another user, the IDE bridge ends with its app, the port belongs to the Docker backend (stop the container in Docker then) or it is a service WebDonkey runs (stop it under Services then).

Clean up orphans

When there are orphaned servers, Clean up orphans (trash can) appears at the top. The dialog Clean up orphaned servers lists every orphan that was matched to a configuration. Each one is checked again and asked to quit. Stop n servers does it, Stop now handles single stragglers. Orphans only recognised by their command are left out: "These orphans were only recognised by their command. Stop them one at a time."

View logs

Logs in a row's menu opens the dialog "Logs of “name”". At the top you pick the Log file, Refresh reads again, Open as tab opens the file in the editor. The end of the file is shown. Logs exist only for clients whose log files WebDonkey knows.

Free and Premium

Viewing and stopping single servers is free. Clean up orphans and Logs are part of Premium. A single orphaned server can always be stopped on its own.

Troubleshooting

What you see Why What to do
A server comes back right after stopping Its client started it again Remove it or turn it off in the client (Configured).
"The server did not react to the request to quit" The process ignores the signal Choose Stop now.
Claude Code no longer finds the tools The server was stopped Type /mcp in Claude Code and choose Reconnect.
An expected server is missing It is not running, or the filter hides it Choose Everything or clear the filter.

See also

Configured Free & Premium

The Configured tab lists what is in the configuration files of your MCP clients, even when none of it is running. Here you check whether a server answers, add new servers, and change, copy or remove entries. Writes always go into the file of the client in question.

Where to find it

MCP window (⌘7), Configured tab. When nothing is configured yet, it says: "Nothing is configured yet. “Add server” writes a server into one of your clients."

What the list shows

Entries are grouped by client and, below that, by scope: User, Local, Project (with its path), Plugin, Managed, Session, Connector, Global or Workspace, depending on what the client knows.

Every row shows name, command or address, and labels:

State Meaning
running / running 2× Runs on this Mac, one copy per session when there are several.
not running A server starts with its client.
remote Does not run on this Mac. A check tells whether it answers.
waiting for approval Claude Code has not been told yet whether this server from the project file may run.
rejected Rejected in Claude Code, it is not started.
off Turned off in the client.
shadowed An entry with the same name elsewhere takes precedence.
off by policy A managed configuration applies, entries from elsewhere are ignored.
invalid The client cannot use the entry like this.

Next to that come the type (stdio, HTTP, SSE), read only for entries that cannot be changed from here, and n notes when something about the entry stands out. If Claude Code reports a missing login for a server, login needed shows up as well.

On the right of the row are Log in (only when a login is missing), a switch Turn on/Turn off (only for clients with an on/off field), Check, and the ⋯ menu with Check through …, Logs, Edit, Copy to other clients, Open file, Log in, Reset approvals and Remove. Whatever a client cannot do is missing from the menu or greyed out with a reason.

Details of an entry

Clicking a row shows:

  • Notes on this entry, for example a variable without a value or a project folder that no longer exists.
  • Command or URL.
  • Variables and Headers: names only. The window never shows values.
  • Source: file and line, with Open file. The file opens as a tab at that line.
  • State with an explanation and the running copies (client, project, PID).
  • Origin: "Added through WebDonkey" for servers you added here or in WebDonkey.
  • Cannot be changed with the reason, for example: set by an administrator, from a plugin, part of a YAML file, or a claude.ai connector (you add or remove those in the claude.ai settings under "Connectors").
  • Login, the result of a check and, where available, the last log lines.

Add a server

  1. Click Add server (+) at the top. The dialog Add MCP server opens.
  2. If a README already has a block to paste, use Take from text: paste the JSON (an mcpServers block or a single entry) and click Fill form. That fills the form, nothing is written yet. If the text holds several servers, you pick one.
  3. Name: what the server is called in the client, for example github.
  4. Type: Local command (stdio), HTTP or SSE.
  5. For stdio: Command, with its arguments in one line, for example npx -y @modelcontextprotocol/server-filesystem ~/Sites. Quotes keep words together. For HTTP and SSE: URL.
  6. Environment variables (stdio) or Headers (HTTP, SSE): name and value per line.
  7. Write to: pick the client and the scope. If the file does not exist yet, file will be created shows next to it. Also show clients that were not found lists clients that were not found on this Mac.
  8. Save.

The window then reports "“name” added to …" and what the client needs now, for example "Restart … so it sees the change." or "Applies to new sessions of …; running ones keep what they started with." If one target fails, the dialog stays open and shows the result per target.

Edit, switch, copy

  • Edit opens "Edit “name”" with the same fields. Values of variables and headers are never shown: a field left empty keeps the value in the file, a new value replaces it.
  • The switch in the row turns the entry on or off in the client.
  • Copy to other clients rewrites the entry into the format of each client you pick, with its real values. Expressions like ${VAR} stay as they are. The button reads "Copy to n places".

Check

Check starts a local server a second time (for HTTP it connects to it) and asks whether it answers and what it offers. The result shows in the details: the number of tools, resources and prompts, the protocol version and "answered after … ms". With Premium you also get the lists themselves, the server's instructions and its error output.

  • If the command comes from a project file, the editor asks first: "Start “name” to check it?" with file and command. Start and check runs it. Only do that if you trust the project.
  • If the server is already running, a second copy that binds a fixed port or holds a lock reports "in use".
  • Some entries cannot be checked, the greyed-out button tells you why, for example "Only the client itself can reach this server."

Check through Claude Code (in the menu, for clients with their own check) asks the client itself. The result reads "Claude Code says:" followed by connected, login needed, failed, no connection, waiting for approval, off or rejected.

Log in

If a server asks for a login, the client handles it. In the editor, Log in runs the client's login command in the terminal, for Claude Code that is claude mcp login <name>, and the client then opens the browser. For clients that log in inside a running session, the details tell you what to type there. With others you log in inside the client itself. You can also copy the command from the details.

Reset approvals and remove

  • Reset approvals (Claude Code, project entries): Claude Code forgets which servers of this project's .mcp.json you approved or rejected, and asks again the next time it starts there.
  • Remove asks "Remove “name”?". If copies are still running, you can have them stopped as well. The entry is taken out of the client's file.

After every write, Undo appears at the top. It works for 60 seconds and only while the editor is running.

What happens in the background

  • Writes go straight into the client's configuration file, for some clients through their own command line tool. WebDonkey makes a backup copy first. If there is no place for it, nothing is written.
  • Existing entries are never overwritten: if the name is taken, the window says so and writes nothing. If the file changed in the meantime, it writes nothing either and reads again.
  • After writing, WebDonkey reads the file back as a cross-check. If that fails, the file stays as it was.
  • Warnings after writing point out risks, for example a secret passed as an argument (visible in the process list) or a file inside a Git repository. A variable (${VAR}) is the better place for a secret.

Free and Premium

  • Free: viewing, Check (counts and response time), Check through …, Open file, Log in, Remove and up to 2 added servers. After that the dialog says "2 of 2 free servers used. Remove one of them or get Premium to add more."
  • Premium: more servers, Several places at once, Edit, Turn on/Turn off, Copy to other clients, Reset approvals, Logs and the full lists when checking.

Troubleshooting

What you see Why What to do
"A server of this name exists here already. Nothing is overwritten." The name is taken in that target Pick another name or edit the existing entry.
The client does not see the new server It only reads its file after a restart or in a new session Follow the hint in the notice.
"The variable … has no value here" The entry uses an environment variable that is not set Set the variable or store the value in the entry.
read only on an entry It comes from a plugin or a policy, or it is a connector Change it where it comes from.
Add server is locked The 2 free servers are used Remove an added server or use Premium.

See also

Clients Free & Premium

The Clients tab shows every MCP client the window knows, the files it looked into and what came of it. This is where you find out why a server is missing from the lists: it sits in a file that was not found, not read or could not be read. Clients the editor does not know yet, you add here yourself.

Where to find it

MCP window (⌘7), Clients tab. The number on the tab is the number of known clients.

Which clients the window knows

Among others Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, Qwen Code, Codex, opencode, Crush, Zed, LM Studio, Goose and Continue, plus your own clients. Clients found on this Mac are at the top. The rest sit folded under Not found on this Mac, with their names in the heading.

What a card shows

Each client is a card with its name, the label your own client for your own ones, and a line below: how many servers its files hold, how many processes are running (or not found) and how the client picks up changes:

Hint Meaning
reads changes by itself The client reads the file again on its own.
restart after changes Restart the client so a change arrives.
changes apply to new sessions Running sessions keep what they started with.
reload after changes Reload the servers in the client or restart it.

The coloured edge of a card shows the worst state of its files. Click the card to unfold its files. Each line names the path, the state, the scope, the number of servers and whether the window can write there:

State Meaning
read All fine.
not there The file does not exist (yet).
unreadable The file is there but cannot be read.
broken The file cannot be parsed, its servers are missing from the list.
too large Larger than 8 MB, not read.
not read In a folder macOS protects (Desktop, Documents, Downloads, iCloud Drive), on an external or network volume, or there are more than 64 project folders at once.

For writing it says can be written, written through the client's own command, one file per server or read only with the reason. On the right of the line are Read now (for files in protected folders or beyond the 64 project folders) and Open file. Files on external or network volumes are never read, because a volume that went away would block the view.

Add your own client

For an MCP client that is not in the list:

  1. Click Add your own client.
  2. Name: at most 64 characters.
  3. Configuration file: the path to the file holding the servers, absolute or starting with ~/, for example ~/.config/my-agent/mcp.json. Files inside another app's container cannot be used.
  4. Format: JSON, JSON with comments or TOML.
  5. Key of the server section: where in the file the servers are, for example mcpServers, servers or mcp.servers.
  6. Optional: Process name, so running servers are assigned to this client, and Login command for Log in. {name} in it stands for the server's name, and the command has to open the browser itself.
  7. Save. The window reads the file right away and reports "“name” saved" with the number of servers found or the state of the file.

The pencil on the card edits the client, the trash can deletes it. Deleting only removes the entry in the window. The client's configuration file and its servers stay untouched.

Free and Premium

Viewing the list, opening files and deleting your own clients always work. Adding and editing your own clients is part of Premium.

Troubleshooting

What you see Why What to do
No MCP client was found on this Mac No known client is installed Install a client or add it here yourself.
A server is missing in Configured Its file is not read or broken Find the file here, choose Read now or fix the error in the file.
Neither the file nor its folder exists Wrong path of your own client Check the path.
The file already belongs to a client in the list A known client reads that file already Use the known client.
An entry has no effect The client has not read the file again yet Follow the hint on the card, for example restart the client.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy