The AdStellar Meta Ads MCP URL is https://app.adstellar.ai/api/mcp, and pasting it into an MCP-compatible AI client lets that assistant analyze, create, and launch Meta campaigns through AdStellar. ChatGPT users can skip manual setup with the approved AdStellar app for ChatGPT, and this guide gives setup steps for six clients: ChatGPT, Claude, Claude Code, Gemini CLI, Grok (xAI API), and Perplexity.
One URL serves every client. What changes is where each tool asks you to paste it, and how it handles sign-in. Menu names and plan requirements shift often, so treat the steps below as the current pattern and confirm labels against each vendor's documentation.
What the AdStellar MCP URL Actually Does
MCP, the Model Context Protocol, is an open standard Anthropic introduced in 2024 that lets AI assistants call external tools in a consistent way. A remote MCP server is a tool provider that lives at a web address. The AdStellar URL is that kind of endpoint. It is not a page: open it in a browser and you will see nothing useful, because it only speaks to MCP clients.
Compare this with the usual workflow of exporting an Ads Manager report, pasting rows into a chat, and asking for advice. The assistant sees a frozen snapshot, and anything it suggests you must carry out by hand. Once connected, the assistant queries live Meta data through AdStellar and can take actions, so analysis and execution happen in the same conversation, much like the shift described in Meta Ads automation vs Ads Manager.
The tools the server exposes map to what AdStellar already does:
- Analyzing past performance: pulling real-time Meta data and surfacing what has worked in your account.
- Building campaigns: assembling a data-backed campaign from that history, with the reasoning behind each choice visible so you can check it.
- Bulk launching: pushing hundreds of ad variations in one pass rather than building them one at a time.
- Creative scoring: rating individual ad elements and flagging fatigue, so the assistant can say which headline, image, or hook is carrying results.
The assistant becomes an interface to the AdStellar Agent, the conversational media buyer, from whichever AI tool you already use.
Before You Connect: Accounts and Permissions Checklist
A few minutes of preparation prevents most failed connections.
- An AdStellar account with your Meta ad account connected. The MCP server acts through your AdStellar account, so it has nothing to work with until that link exists.
- Imported campaign history. Import your existing Meta campaigns so the assistant has past performance to learn from. A connected assistant with an empty account can still build, but its recommendations will be generic.
- A sign-in step you can complete. Expect an authorization prompt the first time a client connects, typically a browser window asking you to log in to AdStellar and approve access. The exact wording and flow vary by client and version.
- The right plan on the AI side. Custom connectors and remote MCP support are not equally available on every plan of every client. As of November 2026 this is still changing, so check each client's current docs before assuming a free tier supports it.
Use one workspace per brand
AdStellar offers unlimited workspaces, and it pays to use them. Agencies in particular should keep each client in its own workspace so the assistant only sees the account you intend. If you manage many brands, a multi-account Meta Ads platform setup keeps reporting clean and reduces the chance of launching something into the wrong brand. Name workspaces clearly, because the assistant will refer to them by name when you ask it to list what it can access.
Add the MCP URL in ChatGPT and Claude
ChatGPT: the approved app
The recommended route is the approved app, which saves you from handling the URL yourself:
- Open the AdStellar app page while signed in to ChatGPT.
- Add or enable the app.
- Sign in to your AdStellar account when prompted.
- Approve the requested access.
- Start a chat, select the app if needed, and run a test prompt.
ChatGPT: manual remote server
Where custom connectors or developer mode are available on your plan, you can instead add https://app.adstellar.ai/api/mcp as a remote MCP server. Look in settings for connectors or developer options, create a new one, name it AdStellar, paste the URL, and complete authorization. Menu names have changed more than once, so verify them against OpenAI's current help pages. If the app link works for you, there is no reason to take this path.
Claude on web and desktop
Claude supports custom connectors, generally found under Settings, then Connectors:
- Choose the option to add a custom connector.
- Name it AdStellar and paste https://app.adstellar.ai/api/mcp.
- Save, then authorize by signing in to AdStellar.
- In a new chat, enable the connector from the tools or connectors menu.
Labels and plan availability differ between individual and team plans, and team owners may need to enable connectors for the organization first.
A first test prompt
Whichever client you use, start with a read-only request:
List my AdStellar workspaces and summarize the last 30 days of Meta performance.
If the assistant returns real workspace names and numbers that match Ads Manager, the connection works.
Add the MCP URL in Claude Code and Gemini CLI
Terminal clients take a command or config entry instead of a settings screen. They suit developers and in-house media buyers who want repeatable, scriptable reporting and a more structured Meta Ads campaign workflow.
Claude Code
The command pattern is:
claude mcp add --transport http adstellar https://app.adstellar.ai/api/mcp
Then start a session and run /mcp. It lists configured servers and lets you authenticate the ones that need sign-in. Complete the browser authorization for AdStellar and confirm it shows as connected. Flags and scopes have evolved, so check them against the current Claude Code documentation before relying on this exact form.
Gemini CLI
Gemini CLI reads MCP servers from its settings.json file. Add an entry under mcpServers with the remote HTTP URL. The key for a remote endpoint has been httpUrl, set to https://app.adstellar.ai/api/mcp, under a name like adstellar. Confirm the key name in the current Gemini CLI docs, since config schemas change. Restart the CLI, run /mcp, and check that the server is listed, completing any authentication it requests.
Troubleshooting terminal setups
- Server not listed or not connected: check the URL character by character, and make sure there is no trailing path or stray space.
- Connected but no tools: re-authenticate from /mcp, then restart the session.
- JSON errors in Gemini CLI: a missing comma in settings.json is the usual culprit, and the server will silently fail to load.
Once it works, a saved prompt or short script can pull the same weekly performance summary every Monday, which is hard to reproduce in a chat window.
Add the MCP URL in Grok (xAI API) and Perplexity
Grok through the xAI API
This is an API-level integration for builders. It is not a toggle in the consumer Grok app. The xAI API accepts remote MCP servers as a tool in the request. The shape looks roughly like this:
tools: [{ "type": "mcp", "server_url": "https://app.adstellar.ai/api/mcp", "server_label": "adstellar" }]
Include that tool in your request to a Grok model and it can call AdStellar's tools during the response. Because the server requires authorization, you may need to supply credentials, commonly through an authorization field or header, and the exact parameter names and supported models are set by xAI. Read the current xAI documentation before building on this snippet, and keep any token out of client-side code.
Perplexity
Where Perplexity offers custom remote connectors, the process mirrors Claude:
- Open settings and find the connectors section.
- Choose to add a custom connector.
- Name it AdStellar.
- Paste https://app.adstellar.ai/api/mcp as the server URL.
- Authorize by signing in to AdStellar, then enable it for your queries.
Availability depends on your plan and platform, and as of November 2026 it is not uniform across web, desktop, and mobile. Check Perplexity's current help documentation to see what your account supports.
When a client falls short
Support for remote MCP is moving quickly, and each vendor implements it a little differently. If one client will not connect, do not burn an afternoon on it. The ChatGPT app and Claude are the most direct routes, and the same AdStellar account and data sit behind all of them.
What to Ask Once You're Connected: Practical Meta Ads Workflows
Diagnostic prompts
- "Which of my active creatives show signs of fatigue, and since when?"
- "Rank my ads by element-level score and tell me which headlines and images are driving results."
- "Explain why my prospecting campaign underperformed last week compared with the prior one."
These prompts work best when the assistant can lean on a solid Meta Ads campaign scoring system rather than raw metrics alone.
Build prompts
- "Build a campaign from my top five winners over the last 60 days."
- "Launch 200 variations combining my best images, headlines, and audiences."
- "Pull the highest-ranked creatives from my library and reuse them in a new retargeting campaign."
Bulk requests like the second one are where it helps to launch multiple Meta ads at once instead of assembling each variation by hand.
Guardrail habits
Connecting an assistant does not mean it should spend money unsupervised. Ask it to explain its reasoning for every campaign it proposes, and review the plan before anything launches. State your goal, daily budget, and any hard limits in the prompt itself, such as a target cost per purchase or a cap on total spend. Vague instructions produce vague campaigns, and following Meta Ads campaign structure best practices gives the assistant a clearer blueprint to work from.
Common mistakes
- Opening the URL in a browser and concluding it is broken. It is an endpoint for clients, not a page.
- Adding extra paths or parameters. Use https://app.adstellar.ai/api/mcp exactly as written.
- Using an unapproved or outdated URL copied from a forum post or old note. Take it from AdStellar.
- Prompting without context, such as "make me some ads," instead of naming the workspace, goal, and constraints.
One URL, Any Client: Connect and Run Your First Analysis
The single URL to add is https://app.adstellar.ai/api/mcp. If you use ChatGPT, the approved AdStellar app is the fastest start, since it handles the connection for you. For every other client, paste the URL where that tool expects a remote MCP server and complete the sign-in.
Pick the client you already work in, connect it, and run one read-only test today: ask for your last 30 days of Meta performance and compare the answer with Ads Manager. Once the numbers match, move on to creative diagnostics and campaign builds with review before launch.
