MCP Server Manager

Workflow

Discover candidate servers

• Check project .mcp.json for existing server configs.

• Check ~/.claude.json for global MCP servers (Claude Code).

• Scan for MCP-related packages in package.json or Cargo.toml .

Choose a registration target

• Project-local: edit .mcp.json directly.

• Global (Claude Code): use claude mcp add / claude mcp remove .

Register the server

• stdio server: claude mcp add <name> -- <command> <args...>

• stdio with env: claude mcp add <name> -e KEY=VALUE -- <command> <args...>

• Or edit .mcp.json directly for project-local config.

Verify registration

• For .mcp.json : read the file and confirm the entry exists.

• For global: run claude mcp list to verify.

Explain reload requirement

• MCP servers are loaded at session start; ask the user to restart the session.

Notes

• Infer type from config: url key = HTTP, command /args keys = stdio.

• When multiple sources define the same name, confirm which to use.

• For stdio servers using npx , the package downloads when the server first runs.

VMark Example

// .mcp.json { "mcpServers": { "tauri": { "command": "npx", "args": ["-y", "@hypothesi/tauri-mcp-server"] } } }