MCP Servers

Model Context Protocol (MCP) servers extend Claude Code with additional tools — GitHub integration, web search, database access, custom APIs, and more. CloudCLI UI lets you manage MCP servers through the UI, and any changes sync directly with your local Claude Code config.

Adding an MCP Server

1. Click the gear icon in the sidebar
2. Select the agent where you want to add MCP servers
3. Go to MCP Servers
4. Click Add Server
5. Enter the server name, command, and any required arguments or environment variables
6. Save — the server is immediately available in your Claude Code sessions

How Sync Works

MCP servers you add via CloudCLI UI are written to your ~/.claude.json config file. This is the same file Claude Code CLI reads. So:

• Adding a server in the UI means it's available next time you run claude in your terminal
• Adding a server via claude mcp add in the terminal means it shows up in the UI
• There is no separate config to keep in sync

Example: Adding GitHub MCP

{
  "name": "github",
  "type": "http",
  "url": "https://api.githubcopilot.com/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_GITHUB_PAT"
  }
}

Scope: User vs Project

MCP servers can be scoped at two levels:

• User scope — available across all your projects (stored in ~/.claude.json)
• Project scope — available only in the current project (stored in .mcp.json in the project root, can be committed to your repo)

CloudCLI UI currently manages user-scoped MCP servers.

Troubleshooting MCP Connections

If a server fails to connect:

• Check that the command or URL is correct
• Verify required environment variables are set
• Restart the session — MCP servers are initialised at session start
• Run claude mcp list in your terminal to verify the server is registered