MCP Configs

MCP (Model Context Protocol) server configurations define external tools and data sources that AI coding tools can connect to — things like database access, API integrations, or custom tool servers. Syllago stores these in a provider-neutral format and converts them to each provider’s native configuration on install.

Syllago Format

MCP configs are stored as JSON with a mcpServers key. Each server entry specifies the command to run, its arguments, and any environment variables:

{
  "mcpServers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"],
      "env": {
        "DATABASE_URL": "postgresql://localhost:5432/mydb"
      }
    },
    "github": {
      "command": "node",
      "args": ["github-server.js"],
      "env": {
        "GITHUB_TOKEN": "..."
      }
    }
  }
}

Each server entry supports:

command — the executable to launch the MCP server
args — command-line arguments passed to the server process
env — environment variables available to the server at runtime
disabledTools — list of tools to disable on this server (supported by Kiro, Windsurf, Roo Code)

disabledTools

The disabledTools field lets you selectively disable specific tools from an MCP server:

{
  "mcpServers": {
    "github": {
      "command": "node",
      "args": ["github-server.js"],
      "disabledTools": ["create_issue", "delete_repo"]
    }
  }
}

This field round-trips through Kiro, Windsurf, and Roo Code. Other providers drop it with a portability warning during conversion.

Provider Support

MCP configs are supported by every provider:

Provider	Supported	Notes
Claude Code	Yes	`.claude.json`, `.mcp.json`
Gemini CLI	Yes	`.gemini/settings.json`
Cursor	Yes	`.cursor/mcp.json`
Copilot CLI	Yes	`.copilot/mcp-config.json`
Codex	Yes	JSON merge
Kiro	Yes	`.kiro/settings/mcp.json`
Windsurf	Yes	JSON merge
Zed	Yes	Uses `context_servers` key
Cline	Yes	VS Code globalStorage
Roo Code	Yes	`.roo/mcp.json`
OpenCode	Yes	`opencode.json` / `opencode.jsonc`
Amp	Yes	`.amp/settings.json`

Format Differences

Most providers use the same mcpServers JSON structure, so conversion is straightforward. The notable exception is Zed.

Zed: `context_servers` Mapping

Zed uses the key context_servers instead of mcpServers in its configuration. Syllago handles this mapping automatically during install and import — no manual adjustment needed.

Zed native format:

{
  "context_servers": {
    "postgres": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-postgres"]
    }
  }
}

When you import from Zed, syllago reads context_servers and normalizes it to mcpServers. When you install to Zed, syllago converts mcpServers back to context_servers.