MCP Server Management In development

Unified management

One central config, synced across CLIs

Switch unifies the configs scattered across each tool’s own mcp_servers.json — Claude Code / Codex / Gemini — and provides visual debugging.

MCP Manager

Open Switch → "MCP Servers" in the left sidebar to see:

Registration status

All currently registered MCP servers, with status running stopped errored

References

Which CLIs reference each server

Call history

The last N tool-call records

Config Format

Switch uses a single central ~/.lurus-switch/mcp.yaml:

servers:
  github:
    command: npx
    args: [-y, '@modelcontextprotocol/server-github']
    env:
      GITHUB_TOKEN: ${GITHUB_TOKEN}
    visible_to: [claude-code, codex]

  postgres:
    command: docker
    args: [run, -i, --rm, mcp/postgres, 'postgres://localhost/dev']
    visible_to: [claude-code]

  kova:
    url: http://localhost:3333
    type: http
    visible_to: [claude-code, codex, gemini]

visible_to drives on-demand delivery

When you switch to any CLI, Switch dynamically generates that CLI’s mcp_servers.json based on visible_to, so each tool only sees the servers assigned to it.

Debugging

Select a server to open the debug panel on the right:

Tools list

All tools exposed by the server, including their input-parameter schema

Manual invocation

Fill in parameters and test directly

Request Log

The complete request/response JSON for recent calls

Restart

Process-level restart

Quick Setup for Common Servers

Switch ships with one-click install buttons — no need to write configs by hand:

Server	Purpose
github	Read/write issues / PRs / files
postgres	Query the database
filesystem	Read/write local files
slack	Send messages / read channels
kova	Kova Agent as a tool
lumen	Lumen Trace / Replay

Sync to Your Team

See Team Sync.

Next Steps

Next steps

Cost MonitoringTeam SyncBack to User Guide