MCP Servers

MCP (Model Context Protocol) servers provide additional tools and resources to Claude Code and Codex. You can configure MCP servers per-project or globally for all sessions.

MCP Scopes

  • Project (.mcp.json) — MCP servers specific to a workspace, stored in the workspace root directory
  • User (~/.claude.json) — Global MCP servers available to all workspaces on the server

Managing MCP Servers

While in a workspace terminal, tap the MCP button in the bottom toolbar. You'll see sections for Project and User MCP servers.

Adding an MCP Server

Tap the + button to add a new MCP server. Choose the server type:

Stdio (Local Process)

Runs a local command on the server as the MCP server. Best for tools installed locally.

  • Server Name — A unique name to identify this MCP server
  • Command — The command to run (e.g., npx, python)
  • Arguments — Command-line arguments for the MCP server
  • Environment Variables — Additional environment variables for the process

Example — adding a filesystem MCP server:

Name:    filesystem
Command: npx
Args:    -y @modelcontextprotocol/server-filesystem /path/to/dir

HTTP (Remote)

Connects to a remote MCP server over HTTP. Best for cloud-hosted tools and services.

  • Server Name — A unique name to identify this MCP server
  • URL — The HTTP endpoint of the MCP server
  • Headers — Custom HTTP headers (e.g., for authentication)

Editing & Deleting

  • Edit — Tap any MCP server in the list to modify its configuration
  • Delete — Swipe left on an MCP server to remove it
Tip

When editing user-level MCP settings (~/.claude.json), ServerCC preserves any fields in the file that it doesn't manage — your other Claude configuration won't be affected.

Configuration Files

MCP configurations are stored as JSON files on the server:

  • Project scope: {workspace}/.mcp.json
  • User scope: ~/.claude.json

These files follow the standard Claude MCP configuration format, so they're compatible with Claude Code on desktop as well.