Agent setup
Native OAuth installation for Claude.ai, Cursor, Codex, and Claude Code, plus the advanced headless fallback.
Use the hosted MCP endpoint:
https://mcp.ad.computer/mcpThe server publishes OAuth protected-resource metadata. Supported clients discover the Ad Computer authorization server, open browser consent, and store their own short-lived access and rotating refresh tokens.
Supported clients
Claude.ai
Ask Claude to use Ad Computer to list your Meta ad accounts, then review one account's performance.
Cursor
In Cursor Agent, ask Ad Computer to list your Meta ad accounts, then review one account's performance.
Codex
codex mcp add ad-computer --url https://mcp.ad.computer/mcp --oauth-resource https://mcp.ad.computer/mcp
codex mcp login ad-computerAsk Codex to use Ad Computer to list your Meta ad accounts, then review one account's performance.
Claude Code
claude mcp add --transport http --scope user ad-computer https://mcp.ad.computer/mcp
claude mcp login ad-computerAsk Claude Code to use Ad Computer to list your Meta ad accounts, then review one account's performance.
Claude.ai
Open the custom connector flow, add the hosted MCP URL, and authorize the workspace. Claude.ai currently uses its pre-registered production client.
Cursor
Use the one-click install button in the Agents launchpad. Cursor supports remote MCP OAuth and uses fixed web/agent and desktop callback forms.
Codex
codex mcp add ad-computer --url https://mcp.ad.computer/mcp --oauth-resource https://mcp.ad.computer/mcp
codex mcp login ad-computerClaude Code
claude mcp add --transport http --scope user ad-computer https://mcp.ad.computer/mcp
claude mcp login ad-computerVerify the connection
Run the same read-only gate in every client:
- Discover Ad Computer tools.
- Call
meta_get_ad_accounts. - Choose an explicit
account_id. - Call
meta_review_account_performance. - Confirm the app says Connected and tested.
Revoke the connection
Revoke the OAuth client in Connections. The next MCP request must fail before you authorize the client again.
Other MCP clients
Other clients may add the hosted endpoint as a remote Streamable HTTP MCP server and attempt OAuth. This is a manual beta path, not a universal compatibility claim.
Advanced headless or stdio path
Use adcom only when native remote OAuth is unavailable:
adcom login --json
adcom whoami --json
adcom mcp inspect-tools --json
adcom mcp serveThe browser may run on a different machine. For a client that cannot use the CLI device flow, the app can generate a short-lived bearer configuration under Advanced · headless · stdio.