Getting started

Create a workspace, connect Meta, authorize an agent with OAuth, and complete the first read-only review.

The self-serve beta uses one OAuth-first path. You do not need to generate or copy a bearer token.

1. Create the workspace

Go to app.ad.computer, create an account, and sign in. Your account is the workspace during beta.

2. Connect Meta

Open Connections and complete Meta OAuth with an identity that can access the ad accounts you want to review.

Meta is the launch acceptance path. Google Ads and TikTok remain available in Connections, but they are not required for the first run.

3. Choose an agent

Open the Agents launchpad, then choose one of the supported clients:

Claude.ai

Open Claude connectors

Ask Claude to use Ad Computer to list your Meta ad accounts, then review one account's performance.

Cursor

Install in 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-computer

Ask 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-computer

Ask Claude Code to use Ad Computer to list your Meta ad accounts, then review one account's performance.

Claude.ai opens its custom connector settings. Cursor uses its native one-click remote MCP install link. Codex and Claude Code use their native remote MCP commands.

In every case, complete OAuth in the browser when the client asks. The client receives short-lived, workspace-bound access with rotating refresh tokens.

4. Run the first review

Ask the connected agent to:

Use Ad Computer to list my Meta ad accounts. Let me choose an account_id, then run meta_review_account_performance for that explicit account. Keep this read-only.

The app advances through:

OAuth authorized
MCP reached
First review completed

When all three are recorded, the client says Connected and tested.

Revoke and reconnect

Open the Authorized AI clients section in Connections and revoke the client. Its next MCP request must fail. Then run the client login command again to reauthorize.

Expired and revoked credentials are hidden by default; use Show expired and revoked to inspect history.

Advanced and headless clients

Use adcom, local stdio, or a generated bearer only when the client cannot complete remote OAuth. Generated bearer credentials default to 24 hours and cannot exceed seven days.

Other MCP clients remain a manual beta path. Ad Computer does not claim universal client compatibility until another client passes the same OAuth, discovery, review, and revocation gate.