MCP
Free & PremiumThe MCP page shows the MCP servers on this Mac: what runs, who owns it and what is configured in which client. MCP (Model Context Protocol) is how AI clients such as Claude Code, Cursor or VS Code get extra tools, for example access to a database, a browser or an issue tracker. Each of those tools is a small server of its own that the client starts or reaches at an address. WebDonkey treats every client the same and shows them all in one place.
WebDonkey knows these clients: Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Gemini CLI, Qwen Code, Codex, opencode, Crush, Zed, LM Studio, Goose and Continue. If yours is missing, add it yourself (Clients).
What you do here
- See which servers run right now and who started them: Running.
- See what the configuration files of your clients contain: Configured.
- Find out why a server is missing: Clients.
- Add a server to a client: Add server.
- Test whether a server starts and answers: Check.
- Stop hanging or orphaned servers: Stop and clean up.
- Log in to a server that asks for it: Log in.
- Edit entries, turn them on and off, copy them to other clients or remove them: Edit, copy, remove.
Page layout
At the top you see a summary, for example 3 running · 12 configured · 1 orphaned. The orphan count only shows when there are orphans. Next to it are the buttons Refresh, Clean up orphans (only when there are orphaned servers) and Add server.
Below are three tabs, each with its count:
| Tab | Content |
|---|---|
| Running | MCP server processes running on this Mac right now |
| Configured | entries in the configuration files of the clients, running or not |
| Clients | every known client with its files and what came of reading them |
On Running and Configured a filter line sits above the list: All and one button per client (once there is more than one), the search field Search MCP servers… and, when project folders are known, the picker All projects. If nothing matches, you see Nothing matches the filter. with Clear filter.
The page reads the state again on its own: every 3 seconds while the window is in front, every 15 seconds while it is visible in the background, and not at all while the page is hidden. Refresh reads at once. If reading fails, the page keeps the last state and says what time it is from.
The same view lives in the MCP tab of the Claude page, limited to the servers of Claude Code.
On the command line
The wd command line (More tools) shows the configured servers in the terminal too:
wd mcp # configured servers with client, scope and state
wd mcp clients # the known clients and their files
wd mcp disable <server> # turn a server off, the entry stays
wd mcp enable <server> # turn it on again
Free and Premium
Free: seeing everything, Stop for a single server, Check with the basic result, Check through Claude Code, Open file, Remove and Log in. You can also add up to 2 servers with Add server. What counts are servers you added through WebDonkey that still exist. Remove one of them and its place is free again.
Premium is needed for: the lists of tools, resources and prompts when checking, Logs, Clean up orphans, adding more than 2 servers, writing to several clients at once, Edit, Turn on and Turn off, Copy to other clients, Add your own client and Reset approvals. Locked actions stay visible and carry · Premium or the Premium badge. A click on one leads to the Premium page. Prices are at webdonkey.io/pricing.
Running Free & Premium
The Running tab shows the MCP server processes running on this Mac right now. A server usually starts together with its client, for example with a Claude Code session, and stays in this list while it runs. At a glance you see which servers use memory and CPU, which run twice and which were left behind when their client ended.
Where to find it
Sidebar › Tools › MCP, tab Running. It is selected the first time you open the page.
How to do it
- Open the Running tab.
- Look at the groups. Each group stands for an owner, for example a Claude Code session with its project folder.
- Click a row to unfold its details.
- Use the buttons at the end of the row to stop the server or open the menu with more actions.
When nothing runs, the tab says: “No MCP server is running right now. A server starts with its client, for example with a Claude Code session, and shows up here while it runs.”
Groups
Servers are grouped by their owner. Fold a group with the arrow in front of its heading.
| Group | Meaning |
|---|---|
| Name of the client, plus session or project | started by this client, with its run time (“for …”) and project folder |
| Started by hand | runs without a client having started it |
| Orphaned | the client is gone, the server kept running (“their client is gone, they kept running”) |
| Service | a service WebDonkey runs itself |
| Check in progress | a copy WebDonkey started right now for a check |
What a row shows
- The name of the server and the kind of connection: stdio (local command), HTTP, SSE, WebSocket or IDE bridge (a bridge built into a development environment).
- Labels for anything special. Hover over one for an explanation:
| Label | Meaning |
|---|---|
| Docker | runs through Docker; only Docker’s client process is visible, the usage is without the container |
| duplicate | a second copy of the same configuration under the same client |
| port open | the port is open; whether an MCP server answers there is only known after a check |
| lock without process | the lock file is still there, the process is not |
| other user | belongs to another user of this Mac |
| not in a configuration | recognised by its command, found in no configuration |
- Below it the command or address. Your home folder is shortened to
~. - On the right the figures: PID, port, run time, memory and CPU in percent.
- A coloured edge on the left: green, yellow for an orphaned server.
Unfolded
| Line | Content |
|---|---|
| Command or URL | the full command or address |
| Process | PID, number of processes, run time, memory and CPU |
| Owner | client, session, project folder, app, PID of the client |
| Matched by | how WebDonkey recognised the process: Matched to a configuration, Recognised by its command or Announced by the app (lock file). A click on the entry jumps to the Configured tab |
| Notes | an explanation of every label, for example “Started through a launcher (npx, uvx …): the server itself is a child process.” |
| Cannot be stopped | why this process cannot be stopped |
Actions
- Stop (square icon): asks the server to quit. If that is not possible, the button is grey and its tooltip gives the reason. More in Stop and clean up.
- The … menu holds:
- Logs (Premium), when the client writes log files (Claude Code and Claude Desktop),
- Show configuration: jumps to the matching entry on the Configured tab and unfolds it,
- Copy command: puts the command on the clipboard.
Filtering
Above the list you filter by client (All or one client), by project (All projects or one folder) and by name with Search MCP servers…. With very many servers (over 300) the groups start folded.
What happens in the background
WebDonkey reads the process list of the Mac, open ports and the lock files of the clients, and only while the page is open and visible. It never reads the environment of the processes, and secrets in command lines are shown masked. Nothing of this leaves the Mac.
Free and Premium
Seeing and stopping single servers are free. Logs and Clean up orphans need Premium.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| A server is missing although its client runs | the client starts it only when needed, or it is a remote server | look at the Configured tab |
| not in a configuration | the process looks like an MCP server but is in no known file | check the command before you stop it |
| A server shows duplicate | two sessions of the same client each started a copy | normal, every session has its own copy |
| “Reading the configuration takes longer than usual.” | a file takes unusually long | the list shows the last state; wait a moment or click Refresh |
See also
Configured Free & Premium
The Configured tab lists every MCP server that is in a configuration file of your clients, whether it runs right now or not. You see which client knows which server, at which scope the entry lives and what state it is in. From here you check, edit, copy and remove entries.
Where to find it
Sidebar › Tools › MCP, tab Configured. From the Running tab, Show configuration jumps straight to the matching entry.
How to do it
- Open the Configured tab.
- Find the client, for example Claude Code. Its entries are grouped by scope, projects with their folder.
- Click an entry to see its command, source and state.
- Pick an action: Check at the end of the row, or one from the … menu.
When nothing is set up yet, the tab says: “Nothing is configured yet. “Add server” writes a server into one of your clients.” How that works is in Add server.
Scopes
The scope says where an entry lives and who it applies to:
| Scope | Meaning |
|---|---|
| User | applies to you in every project (Claude Code) |
| Local | applies only to you in one project (Claude Code) |
| Project | in the project file .mcp.json, travels with the repository |
| Global | the central file of a client |
| Workspace | a client’s file inside the project folder |
| Plugin | comes from a plugin of the client |
| Managed | set by an administrator |
| Session | what a running session was started with (--mcp-config) |
| Connector | a connector of claude.ai |
Connectors of claude.ai are in no file. They show up as soon as Claude Code names them in its own check.
State
| State | Meaning |
|---|---|
| running or running 2× | runs on this Mac, one copy per session |
| not running | a server only starts with its client |
| remote | does not run on this Mac; a check says 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 of the same name at another scope takes precedence |
| off by policy | a managed configuration is in force, entries from elsewhere are ignored |
| invalid | the client cannot use the entry as it is |
More labels on the row: the kind (stdio, HTTP, SSE), read only for entries WebDonkey must not change, login needed when the client reports it, and 1 note or 3 notes when WebDonkey notices something about the entry. Values of variables and headers are never shown.
Unfolded
| Line | Content |
|---|---|
| Notes on this entry | what WebDonkey noticed, for example “The variable X is not set here and has no default.” |
| Command or URL | what is started or called |
| Variables and Headers | names only, never values |
| Source | file and line, with Open file |
| State | the state in one sentence, plus running copies with their PID |
| Origin | Added through WebDonkey when you added the entry here |
| Cannot be changed | why WebDonkey must not change the entry; for plugins with Open plugins |
| Login | whether the server needs a login, with Log in (Log in) |
| Result of the check | shows after Check (Check) |
| Logs | the last log lines, when the client writes any (Premium) |
Actions
At the end of the row:
- Log in, when the client reports a missing login.
- A switch to Turn on and Turn off the entry, for clients with an on/off field (Premium).
- Check starts the server briefly for a test.
In the … menu, depending on client and entry:
- Check through Claude Code (Claude Code only)
- Logs (Premium, Claude Code and Claude Desktop)
- Edit (Premium)
- Copy to other clients (Premium)
- Open file
- Log in or Log in again
- Reset approvals (Premium, Claude Code with a project file)
- Remove
What these actions do in detail is in Edit, copy, remove.
Where WebDonkey does not write
read only marks entries from administrators, plugins and running sessions, connectors of claude.ai and sections in YAML files (Goose, the central file of Continue). The reason is in the unfolded entry. A connector is removed in the settings of claude.ai under “Connectors”.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
| A server is missing from the list | its file was not found, not read or is broken | look at the Clients tab |
| A project is missing | its file is in a folder macOS protects (Desktop, Documents, Downloads, iCloud Drive) | on the Clients tab, click Read now at that file |
| shadowed | an entry with the same name at another scope wins | change the other entry or rename this one |
| “A URL without “type”: Claude Code refuses such an entry.” | the entry lacks its kind of connection | add "type" in the file |
See also
Clients Free & Premium
The Clients tab shows every MCP client WebDonkey knows, the files WebDonkey looked at and what came of it. This is where “why don’t I see server X?” gets its answer: a server that is missing from the lists is in a file that was not found, not read or not readable. You also add clients of your own here that WebDonkey does not know yet.
Where to find it
Sidebar › Tools › MCP, tab Clients.
Layout
Each client is a card. Its header shows the name, for your own clients with the label your own client, and below it a status line, for example “4 servers · 2 processes running · changes apply to new sessions”. The coloured edge shows the worst of the client’s files: green when everything was read, yellow when something was not read, red when a file is broken or unreadable. A click on the header folds the files in and out.
Clients that are not on this Mac are collected under Not found on this Mac. The group starts folded and lists their names.
When a client reads changes
The status line also says when the client notices a change to its file:
| Note | Meaning |
|---|---|
| reads changes by itself | the client reads the file again on its own |
| restart after changes | restart the client |
| changes apply to new sessions | running sessions keep their servers, new ones get the change |
| reload after changes | reload the servers in the client or restart it |
A client’s files
Each file is a row of its own with path, result, scope, number of servers and how WebDonkey writes it.
| Result | Meaning |
|---|---|
| read | read, its servers are in the lists |
| 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 beyond 64 project folders |
WebDonkey reads files in protected folders and projects beyond the 64 only when you click Read now. It never reads external or network volumes, because a volume that went away would block the page.
| How it is written | Meaning |
|---|---|
| written through the client’s own command | WebDonkey uses the client’s own command (for Claude Code claude mcp …) |
| can be written | WebDonkey writes straight into the file |
| one file per server | each server has a file of its own (Continue) |
| read only | WebDonkey changes nothing here; the reason is given |
Open file at the end of the row opens the file in your editor.
Add your own client
For an MCP client that is not in the list:
- Click Add your own client.
- Name: at most 64 characters.
- Configuration file: absolute, or starting with
~/. Files in another app’s container cannot be used. - Format: JSON, JSON with comments or TOML.
- Key of the server section: for example
mcpServers,serversormcp.servers. - Optional Process name (optional): so that running servers can be assigned to this client.
- Optional Login command (optional): for Log in at this client’s servers.
{name}stands for the server’s name. The command has to open the browser itself. - Save.
WebDonkey reads the file at once and reports “4 servers found” or the result of reading. The client shows up with the label your own client. The pencil edits it, the bin deletes it. Deleting only removes the entry in WebDonkey; the client’s configuration file and its servers stay untouched.
Free and Premium
Seeing everything is free, and so is deleting your own clients. Add your own client and editing your own clients need Premium.
Troubleshooting
| Message | What to do |
|---|---|
| “Neither the file nor its folder exists. Is the path right?” | check the path; at least the folder has to exist |
| “The file is there but cannot be read in the chosen format.” | pick another Format |
| “What the key names in the file is not a table of servers.” | correct the Key of the server section |
| “This file already belongs to a client in the list.” | the file is read already, no client of your own is needed |
| “There are too many clients of your own. Delete one first.” | delete one of your own clients |
See also
Add server Free & Premium
Add server writes an MCP server into a client’s configuration without you editing the file by hand. You give the command or address, pick the client, and WebDonkey writes the entry in exactly that client’s format. You can paste the snippet from a server’s README straight in.
Where to find it
Sidebar › Tools › MCP, top right Add server. On Free the button shows where you stand, for example 1/2.
How to do it
- Click Add server. The dialog Add MCP server opens.
- Enter a Name, for example
github. Some clients refuse certain names or keep them for themselves. - Choose the Type:
- Local command (stdio): a program the client starts on your Mac. Under Command, enter command and arguments in one line, for example
npx -y @modelcontextprotocol/server-filesystem ~/Sites. Quotes keep words together. - HTTP or SSE: a server the client reaches at an address. Enter the URL, for example
https://mcp.example.com/mcp.
- Local command (stdio): a program the client starts on your Mac. Under Command, enter command and arguments in one line, for example
- Optional: Environment variables (for stdio) or Headers (for HTTP and SSE). + Variable or + Header adds a row: the name on the left, the value on the right. The value is hidden.
- Under Write to, pick the place: client, scope and file. file will be created means the file does not exist yet.
- Click Save.
The page then says, for example, “github” added to Claude Code · User, plus a sentence on when the client reads the change. Undo takes the addition back for 60 seconds, while the app is running.
Take from text
Many servers ship a ready JSON snippet in their README.
- In the dialog, click Take from text.
- Paste the JSON: an
mcpServersblock or a single entry. - Click Fill form. WebDonkey fills in the form; nothing is written yet.
- If the text holds several servers, pick one (“3 servers found. Which one?”).
- Check the form and save as above.
Fields and options
| Field | Meaning |
|---|---|
| Name | name of the server in the client |
| Type | Local command (stdio), HTTP or SSE |
| Command | program and arguments in one line (stdio only) |
| URL | address of the server (HTTP and SSE only) |
| Environment variables | name and value the server gets at start (stdio only) |
| Headers | name and value sent with every request, a token for example (HTTP and SSE only) |
| Write to | client, scope and file the entry goes to |
Write to first lists the clients found on this Mac that WebDonkey may write to. Also show clients that were not found (3) adds more places, for example the project file of a client nobody here uses but that travels with the repository. Only clients that were found hides them again.
What happens in the background
- For Claude Code, WebDonkey writes through the client’s own command (
claude mcp …), for the other clients straight into their file, for Continue as a file of its own per server. - Before every write WebDonkey makes a safety copy of the file. Without a place for it, nothing is written.
- WebDonkey never overwrites an entry of the same name. If the file changed elsewhere in the meantime, it stops.
- After writing, WebDonkey checks the result. If that cross-check fails, the file stays as it was.
- For the Free count, WebDonkey keeps client, scope, project, name and time of the entry, never the command, address or values.
Security
- WebDonkey never shows values of variables and headers again. When editing, an empty field keeps the value in the file.
- A secret belongs in a variable, not in the command line. WebDonkey warns after writing: “A secret stands as an argument instead of a variable; it shows up in the process list.”
- If the file is in a Git repository and the entry holds values, WebDonkey warns as well. A variable like
${VAR}is the better place for a secret.
Free and Premium
Free can add up to 2 servers, each into one client. Below the form you see where you stand: “1 of 2 free servers used. More with Premium.” When both places are taken, it says “2 of 2 free servers used. Remove one of them or get Premium to add more.” and Save is locked. Only servers you added through WebDonkey that still exist count.
With Premium you add as many servers as you like and write to several places at once. On Free, Several places at once with the Premium badge sits next to Write to, and you can pick only one place.
Troubleshooting
| Message | What to do |
|---|---|
| “No client was found whose configuration WebDonkey can write.” | install a client, or use Also show clients that were not found |
| “A server of this name exists here already. Nothing is overwritten.” | pick another name or edit the existing entry |
| “This client does not accept the name.” | use a name without special characters |
| “This client’s format cannot hold this kind of server.” | pick another Type or another client |
| “The client’s own command line is not installed.” | for Claude Code, set up the claude program |
| “The text is too long (more than 1 MB).” | paste only the server section |
| “No server was found in this text.” | check that the JSON is complete |
See also
Check Free & Premium
Check starts a configured MCP server briefly for a test and asks it what it offers: does it start, does it answer, who is it, how many tools does it have. That tells you whether an entry works before you go hunting in the client. Check through Claude Code, in contrast, has Claude Code check its own servers and shows its verdict.
Where to find it
Sidebar › Tools › MCP, tab Configured. Check is the icon at the end of each row, Check through Claude Code is in the … menu of Claude Code’s entries.
How to do it
- Click Check at an entry. The row unfolds and shows “Check in progress: the server is asked what it offers.”
- Wait for the result. Cancel ends the check early.
- Read the result in the unfolded entry.
If the command comes from a project file rather than your own configuration, WebDonkey asks first: Start “github” to check it? The dialog shows file and command and explains: “This command comes from a project file, not from your own configuration. Checking runs it on this Mac. Start it only if you trust the project.” Only Start and check runs it.
The result
On success the heading shows the name and version the server reports. Below it:
| Item | Meaning |
|---|---|
| 5 tools, 2 resources, 1 prompt | what the server offers |
| Protocol | the MCP version it speaks |
| answered after 340 ms | how fast it answered |
| “2 lines on stdout were not MCP and were skipped” | the server also printed text that is not part of the protocol |
With Premium you also get the lists themselves: every tool, resource and prompt, the server’s Instructions and its error output. If a server offers more than 500 tools, the list is cut off.
If the check fails, WebDonkey names the reason and the stage where it failed (at start, at the handshake, while listing the tools):
| Message | What to do |
|---|---|
| “The command was not found” | install the program or fix the path in the command |
| “The server ended right away” | run the command in a terminal, or look at the error output with Premium; often an argument or a token is missing |
| “No answer in time” | the server starts too slowly or hangs |
| “The variable TOKEN has no value here” | set the variable in the configuration or your shell |
| “The server wants a login” | Log in |
| “Nothing answers at this address” | check the address, start the server |
| “The certificate was not accepted” | check the server’s certificate |
| “The server redirects to another host; that is not followed” | enter the final address directly |
| “What answers is not an MCP server” | the address or command points at something else |
If a server speaks the old SSE transport, WebDonkey only checks whether it answers: “The server answers. It speaks the old SSE transport, so its tools are not asked for from here.”
What cannot be checked
Some entries WebDonkey cannot check itself. The icon is grey then, and the tooltip says why, for example “Only the client itself can reach this server.”, “The server wants a login.” or “The entry is incomplete or invalid.” An entry that asks for a value at start (${input:…}) can also only be started by the client.
Check through Claude Code
Check through Claude Code runs claude mcp list and shows what Claude Code says about each server: connected, login needed, failed, no connection, waiting for approval, off or rejected. The unfolded entry then reads “Claude Code says:” with the state. This check also knows the connectors of claude.ai.
What happens in the background
- For a local command, WebDonkey starts the server a second time, next to a copy that may already run, and stops it again after the check. A server with a fixed port or a lock then reports “in use”. The unfolded entry points this out.
- For a remote server, WebDonkey connects to the configured address, introduces itself as “WebDonkey”, asks for the lists and closes the connection again. It never calls a tool.
- A check may take 20 seconds, 60 seconds for commands run through a launcher such as
npxoruvx, because the launcher often downloads a package first. - Whatever a started command sends to the network itself, such as
npxfetching a package, is up to that program.
Free and Premium
The basic result (does it answer, protocol, number of tools, resources and prompts) and Check through Claude Code are free. The full lists, the server’s instructions and its error output come with Premium.
See also
Stop and clean up Free & Premium
An MCP server that hangs, eats memory or keeps running after its client ended can be stopped here. Stop asks a single server to quit. Clean up orphans stops all servers whose client is gone in one go. A process is only ended hard when you explicitly want that.
Where to find it
Sidebar › Tools › MCP, tab Running: Stop at the end of each row. Clean up orphans sits top right as soon as there are orphaned servers.
Stopping a server
- Click Stop in the server’s row.
- The dialog Stop “github”? tells you first what that means:
- For Claude Code: “Claude Code loses the tools of this server until you choose /mcp → Reconnect there.”
- For other clients: the client loses the tools and may start the server again right away.
- Without a client: “The server is asked to quit. Whoever uses it loses its tools.”
- Read the warnings, if any, and the command shown.
- Click Stop. The page then reports ““github” was stopped” or ““github” was already gone”.
When it does not react
If the server ignores the request, the dialog lists the PIDs still running (“Still running: PID 4711”) and offers Stop now. That ends it hard (SIGKILL). It never happens by itself. The message afterwards is ““github” was stopped hard”.
Warnings in the dialog
| Warning | Meaning |
|---|---|
| “The server is working right now (CPU above 5 %). A call in progress is cut off.” | a request of the client is cut off |
| “Started through Docker: if it has to be stopped hard, the container may keep running.” | check with docker ps afterwards |
| “A launchd service: macOS may start it again.” | macOS may restart the process |
| “The server started a client of its own, which ends with it.” | a child process ends too |
| “Not recognised from a configuration, only by its command. …” | look at the command before you stop it |
What cannot be stopped
The button is grey when WebDonkey must not stop the process. The reason is in the tooltip and in the unfolded entry under Cannot be stopped:
- WebDonkey itself or one of its own processes,
- a client rather than a server,
- a process of another user of this Mac,
- a bridge built into an app (“the bridge ends with its app”),
- a port that belongs to Docker’s backend (stop the container in Docker),
- a service WebDonkey runs (stop it on the Services page),
- a process macOS does not let you stop.
Clean up orphans
A server is orphaned when its client is gone but it keeps running. That happens when a client crashes or is killed.
- Click Clean up orphans at the top.
- The dialog Clean up orphaned servers lists the servers affected: “These servers lost their client and kept running. Each one is checked again and asked to quit.”
- Click Stop 3 servers (the number adapts).
- Servers that do not react get their own Stop now in the list.
Only orphans that WebDonkey recognised from a configuration are cleaned up. Servers recognised only by their command you stop one at a time (“These orphans were only recognised by their command. Stop them one at a time.”).
What happens in the background
WebDonkey sends the signal to each single process of the server, never to a whole process group, so the client itself is spared. Before every signal it checks PID and start time again, so it never hits another process that got the same PID in the meantime.
Logs
With Premium, Logs shows a server’s log file, when the client writes one. Claude Code and Claude Desktop do. The unfolded entry on the Configured tab shows the last lines, Show all opens the dialog. Logs in the … menu of a row opens the same dialog Logs of “github”. It shows the end of the file, error lines in red. The Log file picker switches to an older file, Refresh reads again, Open file opens the file in your editor. Without lines it says “No log lines. The client writes them while the server runs.”
Free and Premium
Stop and Stop now for a single server are free. Clean up orphans and Logs need Premium.
See also
Log in Free
Some MCP servers ask for a login, usually in the browser, for example for a service like GitHub or an issue tracker. Log in starts the login the way the client that owns the entry does it. This is free.
Where to find it
Sidebar › Tools › MCP, tab Configured. When an entry needs a login, Log in sits right in its row. Otherwise you find Log in or Log in again in the … menu and in the Login line of the unfolded entry.
Whether a login is missing
- For Claude Code, WebDonkey asks the client itself. While you look at the Configured tab this happens on its own, at most every ten minutes. Above the list you then see “2 servers want a login” or “Claude Code reports no missing login.”, next to it Check logins to ask again at once. A row with a missing login carries the label login needed.
- For the other clients it only shows when you check the server: if the server turns the check away without a login, the entry says “This server asks for a login: the check was turned away without one.”
How to do it
- Click Log in at the entry.
- What happens next depends on the client:
- Browser (Claude Code, Cursor, Codex, opencode, your own clients with a login command): the client opens the browser. The button shows Waiting for the browser…, below it “Claude Code opens the browser. Finish the login there; this waits for up to five minutes.” Cancel stops it.
- Terminal (Gemini CLI, Qwen Code): you log in inside a running session of the client. The click unfolds the entry. It shows the command that starts the client in a terminal and, under Type there:, the line for the session, for Gemini CLI for example
/mcp auth github. Copy copies either. - Inside the client (Claude Desktop, VS Code, Windsurf, Crush, Zed, LM Studio, Goose, Continue): the client asks in its list of MCP servers as soon as it connects to the server. WebDonkey brings the app to the front where it can.
- Finish the login in the browser or the client.
- The entry then says Logged in to “github” or, when only the client was opened, “Claude Desktop is open. Log in to “github” there.”
For clients with a browser login, the entry also shows under Or in a terminal: the command that starts the login yourself in a terminal, with Copy.
What happens in the background
WebDonkey runs the client’s login command, for Claude Code claude mcp login <name>. The login itself runs between the client and the provider of the server. WebDonkey neither sees nor stores credentials. After a login through Claude Code, WebDonkey asks the client again so the row shows the new state.
Troubleshooting
| Message | What to do |
|---|---|
| “The login was cancelled” | click Log in again |
| “The login in the browser was not finished within five minutes.” | start again and finish in the browser without delay |
| “A login for this server is waiting in the browser already.” | finish or cancel the open login in the browser |
| “The client could not be opened. Is its app installed?” | install the client’s app |
| “There is nothing to start for this login. Log in inside the client itself.” | log in inside the client |
For a client of your own, enter a Login command (optional) under Clients so that Log in works there.
See also
Edit, copy, remove Free & Premium
Entries in a client’s configuration can be changed right on the MCP page: edit them, turn them on and off, copy them to other clients, remove them and, for Claude Code, reset a project’s approvals. WebDonkey always writes in the format of the client in question and makes a safety copy first.
Where to find it
Sidebar › Tools › MCP, tab Configured. The actions are in the … menu at the end of a row, the on/off switch sits right in the row.
Where an entry cannot be written (Managed, Plugin, Session, a connector of claude.ai, a section of a YAML file), the row says read only. Edit and remove are missing then; the reason is in the unfolded entry under Cannot be changed.
Edit
- … menu › Edit. The dialog Edit “github” opens, with client and scope as its subtitle.
- Change Name, Type, Command or URL, Environment variables or Headers.
- Click Save.
Values of variables and headers arrive empty, the field says “leave empty to keep”. An empty field keeps the value in the file, a new value replaces it. The page then reports ““github” saved in Claude Code · User” and when the client reads the change.
Turn on and off
The switch in the row turns an entry on or off without deleting it. That only works for clients whose format has an on/off field: Codex, opencode, Crush and Zed. A turned-off entry shows the state off.
Copy to other clients
- … menu › Copy to other clients.
- In the dialog Copy “github” to other clients, pick the places. Several are possible.
- Click Copy to 2 places (the number adapts).
The entry is rewritten into each client’s own format, with its real values. Expressions like ${VAR} stay as they are. Because clients write them differently, WebDonkey warns afterwards: “Expressions like ${VAR} were copied word for word; clients write them differently.”
Remove
- … menu › Remove.
- The dialog Remove “github”? shows the command or address and explains: “The entry is taken out of the client’s configuration. “Undo” brings it back for 60 seconds.”
- If the server is running, you can tick Also stop the copy that is running now (with several copies “Also stop the 2 copies that are running now”).
- Click Remove.
After removing, the message at the top offers Undo. That works for 60 seconds and only while the app is running. If a copy keeps running, the page reports “One copy of “github” is still running”. It ends with its session. For Continue, the server’s file goes to the Trash.
Reset approvals
Claude Code asks whether servers from a project’s .mcp.json may run, and remembers the answer. Reset approvals makes Claude Code forget those answers:
- … menu › Reset approvals (for entries of the Project scope).
- Confirm Reset the approvals for “shop”?.
The page then says “Claude Code asks again the next time it starts there.”
What happens in the background
- For Claude Code, WebDonkey writes through
claude mcp …, for the other clients straight into the file. - Before every change WebDonkey makes a safety copy and checks the result afterwards.
- If the file was changed by someone else in the meantime, WebDonkey writes nothing: “The file was changed by someone else in the meantime. Nothing was written.”
- Running sessions keep the servers they started with. A client reads changes, depending on its kind, by itself, after a restart or for new sessions.
Free and Premium
Remove and Open file are free. Edit, Turn on and Turn off, Copy to other clients and Reset approvals need Premium. On Free these actions stay visible with · Premium, and the Premium badge stands in place of the switch.
Troubleshooting
| Message | What to do |
|---|---|
| “The entry changed in the meantime. Nothing was written; the list is being reloaded.” | try again after the reload |
| “Entries of this client have no on/off field.” | remove the entry instead of turning it off |
| “The name appears twice in the file. Fix that in the file first.” | open the file and remove the duplicate |
| “Too late: the old entry is no longer kept.” | the 60 seconds for Undo are over |