Choose Where Servers Live
The location picker at the top of the tab chooses which configuration you are editing:- Global: every workspace on this host.
- A workspace: servers for that project only. Pick one of this host’s workspaces, or browse to add one.
Add A Server
1
Open the dialog
Click Add MCP server.
2
Choose the transport
Remote is the default. Choose Local (stdio) for a command the host launches.
3
Fill in the server
Enter a Name, then the transport’s settings:
- Remote: the Server URL, the Transport protocol (HTTP or SSE), and Authentication: None, Header (custom headers), Env var (an environment variable that holds the token), or OAuth (with an optional client ID and resource). The options depend on the provider.
- Local (stdio): the Command, its Args, and any Env vars.
4
Add it
Click Add server, then check the server’s status.
Server Status
Manage A Server
Each server row has actions for that server:- Sign in, Re-authenticate, and log out, for servers that use OAuth, where the provider supports it.
- Refresh checks the server again.
- Delete removes it after you confirm.
- An on/off switch, for providers that support one: OpenCode, Traycer Inference, OpenRouter, Hugging Face, Grok, Kiro, Droid, Kimi, Kilo Code, Oh My Pi, and Cursor (for workspace servers only). Claude Code, Codex, Copilot, Qwen Code, and Amp have no per-server switch; delete a server to stop using it.