MCP Service Adset
The Adset.Pro platform provides a public MCP service (Model Context Protocol) through which language models (ChatGPT, Claude and compatible clients) work with your Adset.Pro account: they request statistics, build reports and dashboards, and read campaigns, flows, offers, PWAs, push notifications, autorules, the Meta / TikTok section and billing.
The set of tools a client sees depends on the scopes of the key or OAuth connection:
Scope | What it allows |
|---|---|
| Statistics ( |
| Report presets and custom dashboards: reading and creating/changing. Reports and dashboards cannot be deleted via MCP |
| Reading account objects (campaigns, flows, offers, affiliate networks, landings, PWAs, pixels, domains, sources and more) and finding them by name or id |
| Creating objects of the matching type and changing campaigns |
| Reading push notifications and push groups |
| Autorules: reading and changing |
| The Meta / TikTok section: profiles, ad accounts, campaigns, ad sets, ads and their statistics. Read only; off by default |
| Billing transactions |
| Searching and reading knowledge base articles |
Base URL of the MCP server: https://app.adset.pro/mcp
Two authentication methods are supported:
OAuth 2.0 (PKCE) — for ChatGPT, Claude (connectors) and other clients that take the user through the consent screen themselves. No tokens need to be copied manually.
Personal API key (
mcp_…) — for Claude Code, Cursor and any clients with a fixed Bearer token.
Below are step-by-step instructions for both scenarios.
Connecting to ChatGPT (OAuth)
ChatGPT connects to the MCP server on its own via OAuth 2.0 with PKCE. No tokens need to be copied manually — the user signs in to Adset.Pro through the standard consent screen.
Step 1. Enable developer mode
This step is required — without developer mode, the "Add app" item does not appear in the ChatGPT settings.
Open ChatGPT → Settings.

Go to Apps & Connectors.

Open Advanced settings.

Turn on the Developer mode toggle.
Step 2. Add the Adset.Pro app
Go back to Settings → Apps.
Click Add app / Create.

Fill in the fields:
Name:
Adset.ProDescription:
Adset.Pro connectorMCP server URL:
https://app.adset.pro/mcpAuthentication:
OAuth
Click Connect / Add.
Step 3. Authorization and consent
ChatGPT opens a popup with the https://app.adset.pro/oauth/authorize screen:
If you are not signed in yet, sign in to your Adset.Pro account.
On the consent screen you will see your account name and the list of requested scopes (what they allow — see the table above).
Click Approve.

After approval, the window closes automatically. The app in the ChatGPT settings switches to Connected.
Step 4. Usage
Open a new chat and ask ChatGPT to use the tool, for example:
"Show campaign statistics for the last 7 days via Adset.Pro — clicks, cost, ROI."
ChatGPT will call query_stats with the right parameters and render a table.
Revoking access
To revoke the token from ChatGPT:
In ChatGPT: Settings → Apps → Adset.Pro → Disconnect.
On the Adset.Pro side: Profile settings → MCP Keys — the issued OAuth client is shown in the list (the
OAuth clientssection appears only if you have such connections).
Connecting to Claude
Claude (web, Desktop and mobile app) connects as a connector via OAuth — no token is needed:
In Claude, open Settings → Connectors and click Add custom connector.
Enter a name, for example
Adset.Pro, and the URLhttps://app.adset.pro/mcp.Click Connect and confirm access on the Adset.Pro consent screen (as in step 3 for ChatGPT).
Claude Code (CLI) connects with a personal API key (how to issue one — in the next section):
claude mcp add --transport http adset https://app.adset.pro/mcp \
--header "Authorization: Bearer mcp_YOUR_TOKEN_HERE"
Check:
claude mcp list
The list should show the adset entry with the connected status.
Personal API key (Claude Code, Cursor and other clients with a Bearer token)
You issue this token yourself in your Adset.Pro profile settings. The full token is shown only once — right after it is created. Keep it in a safe place (a password manager). It cannot be recovered — only reissued (rotate).
Step 1. Issuing an API key in Adset.Pro
Sign in to your Adset.Pro account: https://app.adset.pro.
In the upper right corner, click the avatar → Settings.

Open the MCP Keys tab.

Click Create API Key.
Fill in the form:
Name — any key name, for example
Claude Code.Scopes — select the ones you need. For statistics,
Query Stats,Get MetadataandExport CSVare enough; for reports and dashboards, account objects, Meta / TikTok (Read Ads) and other sections, turn on the matching scopes (see the table above).Expires in — validity in days. Leave empty for a key that does not expire.
Click Create.

A dialog shows the token once, in this format:
mcp_a1b2c3d4e5f6...Copy it with the Copy button and close the dialog.
Step 2. Connecting in Cursor
Cursor → Settings → MCP → Add new MCP server.
Enter:
Name:
adsetType:
httpURL:
https://app.adset.pro/mcpHeaders:
Key:
AuthorizationValue:
Bearer mcp_YOUR_TOKEN_HERE
Save and restart Cursor.
Step 3. Checking the connection with curl
If something does not work, a quick check from the terminal:
curl -i https://app.adset.pro/mcp \
-H "Authorization: Bearer mcp_YOUR_TOKEN"
The expected response is 200 OK or 400 Bad Request (without an MCP request body). A 401 Unauthorized response means the token is invalid, revoked or expired.
Managing keys
In Profile settings → MCP Keys you can:
Create new keys (
Create API Key).Edit scopes — turn on new scopes for an issued key, for example for reports and Meta / TikTok.
Reissue (rotate, ↻ icon) — the old token is revoked at once and a new one is issued.
Revoke (Delete, bin icon) — the token stops working immediately.
View the name, prefix, scopes, status, last use time and expiry date.
Scopes and limits
What each scope allows is in the table at the beginning of the article. The ads:read scope is off by default for MCP keys and OAuth apps. An OAuth connector connected before a scope appeared has to be reconnected to get it.
Every request automatically applies security filters by teamId and the user's role — the client receives only the data the user can access in the account and can perform only the actions allowed for the role.
Limits:
query_stats.limit— at most 1000 rows per request; for larger samples useexport_csv.export_csv— a soft limit of 100,000 rows (can be extended for specific plans).
Common errors
Symptom | Cause and solution |
|---|---|
| The token is revoked, expired or copied with a space. Reissue the key. |
ChatGPT or Claude: "connection error" after Approve | The authorization code expired (>10 min) or the client changed the |
ChatGPT does not see the tools | Developer mode is off, or the app was not approved in the OAuth window. |
| The key does not have the needed scope. Turn it on in the key's scope settings; reconnect an OAuth connector that was connected earlier. |
Empty tables in responses | The account has no access to the requested team/teamId — check the permissions in the account. |
More troubleshooting — in FAQ — MCP connection.
Useful links
Public OpenAPI specification: https://app.adset.pro/openapi.json
OAuth Authorization Server Metadata: https://app.adset.pro/.well-known/oauth-authorization-server
OAuth Protected Resource Metadata: https://app.adset.pro/.well-known/oauth-protected-resource
