MCP Management

MCP management lets a workspace curate a list of MCP servers — the tools and integrations Claude Code can use — and inject them into every member's session automatically. Add Linear, Context7, a database connector, or any custom server once, and the whole team gets it on their next launch.

What a managed MCP server is

The Model Context Protocol (MCP) is how Claude Code connects to external tools. A managed MCP server is one your workspace defines centrally instead of each member hand-editing their own .mcp.json. SuperClawd supports two transports:

stdio — a local command (e.g. npx) with arguments and environment variables.
http — a remote server reached by URL, with request headers.

The preset catalog

The fastest way to add a server is the catalog. Click Add MCP and pick a preset — currently Linear and Context7 — and the transport config is filled in for you. Presets that require a key prompt you for it; the rest (like Linear, which signs in via your browser) work with no extra setup. You can also choose Custom server to configure command/args/env (stdio) or url/headers (http) yourself.

Secrets are encrypted

Arguments, environment variables, and headers often carry secrets (API keys, connection strings). SuperClawd encrypts those values at rest and only ever sends them, decrypted, to your authenticated CLI. Read-only members see secret values masked in the app.

Where secrets end up

To launch a server, Claude Code reads its config from disk. The CLI writes the decrypted config into a per-launch plugin folder on your machine, which is cleaned up when the session ends. We keep your secrets safe on our side; once they're on your machine, normal local-machine security applies.

How they reach your session

When you launch superclawd, the CLI fetches your workspace's enabled MCP servers and adds them to the generated plugin manifest. Claude Code then starts each server natively, and their tools are auto-approved (they're admin-curated, so they don't prompt). Because MCP servers are configured at startup, changes apply on each member's next launch.

Enabled, experimental, and favorites

Each server has two toggles, plus a favorite:

Enabled — turn a server off without deleting it; disabled servers aren't injected.
Experimental — only inject the server for members running in experimental mode. Use it to trial a new server before rolling it out to everyone.
Favorite — star a server to keep it at the top of the list (a personal quick-find marker; it doesn't change what's injected).

Naming & limits

Name — kebab-case, must start with a letter, max 30 characters (used as the server key).
Arguments & environment variables — up to 5 each per server.
Per workspace — 1 server on the free tier, 25 on paid.

Who can manage

Owners, admins, and maintainers can add, edit, enable/disable, favorite, and delete MCP servers. Members get the list read-only, with secret values masked.