Adding an MCP server in Claude Code
Claude Code adds MCP servers through a CLI command. For a remote server, the basic form is:
- claude mcp add <name> --transport http <server-url>
- For a local/stdio server: claude mcp add <name> -- <command> <args>
- Claude Code stores the configuration in ~/.claude.json
- Restart any open Claude Code sessions after adding a server for the tools to appear
Adding an MCP server in Claude Desktop
Claude Desktop reads MCP server configuration from a JSON config file rather than a CLI command. Open Claude Desktop settings, find the Developer or MCP section, and either edit the config file directly or use the in-app "Add connector" flow if the server supports remote connections.
For remote MCP servers specifically, most providers — including MCP Ads — support adding the server as a custom connector by URL directly inside Claude Desktop or Claude.ai, without touching a config file at all.
Adding a remote MCP server in Claude.ai
In Claude.ai, go to Settings → Connectors → Add custom connector, paste the MCP server URL, and approve the connection. For servers that require account authorization (like ad platforms), you will be prompted to connect each underlying account through browser-based OAuth after the server itself is added.
If the MCP server tools do not show up
This is the most common point of confusion after running claude mcp add or adding a connector. A few checks resolve most cases.
- Restart the Claude session completely — a simple reload sometimes is not enough
- Check that the server URL or command has no typos and that any required environment variables are set
- For remote servers, confirm the OAuth/account-connection step was completed, not just the server-add step
- Run claude mcp list (Claude Code) to confirm the server is registered before troubleshooting further
