MCP servers & catalog
Connect Model Context Protocol servers over stdio, SSE, or Streamable HTTP — with a curated 26-server catalog and OAuth support.
Configuration
Workspace servers are configured in .deyin/mcp.json; legacy user-level configs migrate automatically on upgrade. Environment interpolation supports ${env:NAME}, ${workspaceFolder}, and ${userHome} in commands, URLs, and headers.
Transports & tools
stdio, SSE, and Streamable HTTP transports are supported. Discovered tools register as mcp__<server>__<tool> and pass through Deyin's permission engine like any other tool.
Catalog & OAuth
Settings → MCP lists 26 curated servers — Stripe, Cloudflare, Vercel, GitHub, Supabase, Linear, Sentry, and more — each installing into an isolated module directory. Catalog servers that require OAuth use native browser consent with PKCE; a loopback listener captures the callback and state is validated to prevent CSRF. Tokens are stored encrypted on-device, and the settings page shows auth status with revoke + re-auth support.
Transports
stdio — the server is spawned as a child process; best for local tools and CLIs.
SSE / HTTP — the server runs remotely; best for shared team resources and hosted tools.
All transports support OAuth where the server requires it. Tokens are stored in the OS keychain like every other credential.
Configuration
The built-in catalog (~26 curated servers) can be enabled from Settings → MCP with one click. Anything you add manually lives in .deyin/mcp.json and overrides catalog entries with the same name.
.deyin/mcp.json
{
"servers": {
"github": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"]
},
"docs": { "url": "https://docs.internal/mcp" }
}
}