Roaspy MCP Server
Connect your AI tools to Roaspy using the Model Context Protocol. Ask about
revenue, ROAS, leads, campaigns and contacts in plain English.
Streamable HTTP
Beta: Roaspy MCP is in beta. Features and tools may change, and you may
run into issues. If something doesn't work, contact Roaspy customer support.
The Model Context Protocol (MCP) is an open standard that lets AI assistants
like Claude, Cursor and ChatGPT securely connect to external data sources. The Roaspy MCP server
exposes your Roaspy ad attribution and analytics data as a set of tools the assistant can call on your behalf,
so you can simply ask, "How are my Meta ads doing this week, with campaign names?" and get a real answer.
Installation
The server speaks the Streamable HTTP transport. Point any MCP-compatible client at:
https://mcp.roaspy.com/mcp
Claude Desktop & Cursor
Add this to your MCP configuration file:
{
"mcpServers": {
"roaspy": {
"type": "http",
"url": "https://mcp.roaspy.com/mcp"
}
}
}
Claude.ai (web)
- Open Settings -> Connectors.
- Click Add custom connector.
- Paste
https://mcp.roaspy.com/mcp and save.
Authentication
When you add the connector, your client opens a Roaspy sign-in page. Log in with your
Roaspy account - there is no API key to copy or paste.
- Add the connector and sign in to Roaspy when prompted.
- Ask your question. The assistant lists your businesses and lets you pick one
(if you have only one, it asks before using it), then reuses it for the conversation.
- You can only access businesses your Roaspy account belongs to.
Shortcut: include your business ID in the first prompt, e.g.
"How are my Meta ads doing the last 7 days, with campaign names? Business ID: bus_xxxx"
Analytics & stats
Create a Meta (Facebook/Instagram) single-image ad, based on what has actually worked
for your business in Roaspy. The assistant acts as an advisor: it suggests from your data,
explains why, and you decide. Everything is created PAUSED. Nothing spends
money until you approve publishing.
The flow (9 steps): 1. research your Roaspy data -> 2. ask which ad account,
Page, goal, budget and audience -> 3. write the ad text -> 4. you approve the plan
-> 5. build it, paused -> 6. show what Meta saved, with a preview link -> 7. you approve
publishing -> 8. re-check everything against the plan -> 9. publish.
The assistant cannot delete anything.
Budgets: how it really works
- Your choice. There is no budget limit in the server. You pick the daily budget.
- Your ad account's currency. Each ad account has one fixed currency (e.g. USD, EUR).
The assistant reads it from Meta and shows every budget in it. It never asks you for a currency.
- Normal money, never cents. The assistant sends the amount you said (e.g. 20).
The server converts it to Meta's smallest unit (20 USD -> 2000 cents; currencies without cents,
like JPY, stay 20). The assistant never does this math.
- Checked before going live. When publishing, the server reads the daily budget
Meta has saved and only turns the ad on if it matches the amount you confirmed. If it does not
match, nothing is published.
- Start time. Unless you ask to start right away, an ad set starts at the next
midnight in the ad account's timezone, not the moment it is published.
- Lifetime budgets cannot be published by the assistant yet. Turn those on in Ads Manager.
- Meta's minimums apply. If the budget is below Meta's minimum, Meta refuses it
and the assistant shows you Meta's message.
Meta tools
All figures (revenue, ROAS, sales) always come from Roaspy, never from Meta.
Campaigns
Reports
Funnels & products
Purchases
Tracking links
Custom metrics
Business & integrations
Tips & gotchas
Security
A few good practices:
- Only connect the MCP server in AI clients you trust.
- You sign in with your Roaspy account; this server never sees or stores your password.
- Be cautious with prompts that mix untrusted content (e.g. pasted emails) with tool access. Prompt injection is a real risk for any MCP server.
- To revoke access, remove the connector from your AI client or sign out of Roaspy.