Claude Code adds MCP servers from the command line. One command, saved to your config, and every terminal session afterwards has your ad accounts available.
Add the server
Run this once in any terminal where you use Claude Code. The transport is HTTP because MCP Ads is a remote server rather than a local process.
Terminal
claude mcp add --transport http mcp-ads https://mcp-ads.com/mcp-slim
Note
The configuration is written to ~/.claude.json and persists across sessions. You add it once per machine, not once per project.
Authorise and verify
Complete the OAuth flow
The first tool call opens a browser window to authorise. Approve it once.
Check it registered
List the configured servers to confirm the entry exists and points at the right URL.
Terminal
claude mcp list
Restart open sessions
Any Claude Code session started before you added the server will not see the tools until it restarts.
Why the terminal is a good fit
Scriptable: pair ad-account queries with the rest of your shell workflow
The same skills work here as in the desktop app — they are plain instructions, not a client feature
Long-running audits are easier to leave running and come back to
claude mcp add --transport http mcp-ads https://mcp-ads.com/mcp-slim — the name "mcp-ads" is just the local label, so you can call it something else if you prefer.
Do I need to run it in every project?
No. It is saved to ~/.claude.json at the user level and applies to every session on that machine.
Is there an npm package to install?
No. MCP Ads is a remote server you point a client at, so there is nothing to install and no API key to manage. If you find instructions telling you to npx-install a package for MCP Ads, they are out of date.
Ready to connect?
Start free, connect the platforms you use, and run your first workflow from Claude in minutes.
Claude Code
Claude Desktop / Web