Your catalogue, open to AI shoppers.
See how
Cursor, connected to your accounts.
22 tools, 20 of them on by default. Add one file to your project and Cursor handles the sign-in.
{
"mcpServers": {
"cresva": {
"url": "https://cresva.ai/mcp"
}
}
}22 tools, 20 of them on by default
Rendered from the same manifest the server registers, so this page cannot advertise a tool Cursor will not be offered. The two held back need a permission you turn on yourself.
list_brands
Every brand on the account with its connected platforms and last sync.
list_campaigns
Every campaign that delivered in a window, with its id, platform and spend.
get_campaign_metrics
Spend, ROAS, CPA, CTR and more, by account, campaign, adset or ad.
compare_campaigns
Campaigns, adsets or ads side by side for A/B calls and budget decisions.
detect_anomalies
CPA spikes, ROAS drops and spend surges, with severity and likely cause.
get_pacing_status
Whether spend is on pace against monthly targets, with end-of-month projections.
forecast_performance
A stored forecast with its confidence interval, or an explicit statement that none exists.
get_benchmarks
Industry benchmark CTR, CVR, CPC and ROAS to compare a brand against.
get_budget_recommendation
Suggested budget shifts under CAC, ROAS and minimum-spend constraints.
ask_cresva
The fallback: a marketing question in plain language when no specific tool fits.
get_profit
Did the brand make money: contribution margin, break-even ROAS and the SKUs losing money.
get_memory
What Cresva has learned about a brand: patterns, past decisions and how they turned out.
list_approvals
What is waiting on a human decision, and what was recently decided.
discover_storefront
What a brand's agent-readable storefront publishes, and what it supports.
search_products
Search a storefront's catalogue the way a shopper would ask.
list_products
Page through a storefront's catalogue with the offer fields agents read.
get_product
One product in full, including price, currency and availability.
compare_products
Two to five products from one brand, side by side on the fields agents read.
get_trust_score
The trust signals a storefront publishes about itself, and its tier.
scan_store
Whether an AI agent can find, understand and buy from any storefront. No API key, works on stores you do not own.
20 of 22 on by default. Off until you say so: propose_budget_change, negotiate_price.
Four steps inside Cursor
Add .cursor/mcp.json to your project
Drop the block above into .cursor/mcp.json at the root of your repository. That is the whole configuration: no key, no command, no arguments.
Type / in a Cursor chat and open MCP
Cursor reads the file and lists cresva there. Enable it if it is not already on.
Authorize in the browser
Cursor opens Cresva's consent screen. Choose which brands it may read and confirm, and the server shows as connected.
Ask in a Cursor chat
Try "list my Cresva brands". The tools are available to the agent from that point on.
What leaves your machine, and what does not
A remote connector talks to us directly over HTTPS, holding a token you granted and can revoke from your settings at any time.
What it may touch
Only the brands you pick on the consent screen. Of the 22 tools, 20 are reads and are on by default.
No key to manage
You authorise the connection instead of pasting a credential, so there is nothing to store or rotate, and revoking it in your Cresva settings stops it at once.
Calls are rate limited, and the published numbers are the enforced ones: 10/minute anonymously per IP, 60/minute with a public key, 300/minute with an API key, and 10,000/minute across every caller for one brand. Over the limit you get a 429 with a Retry-After header.
The same tools, whichever assistant you use
Every door below reaches the same server and the same permissions. They differ only in where you paste the URL.
Questions
Do I need a Cresva account?
Yes, for anything about your own accounts. The connector signs you in to Cresva and you choose which brands it may read.
Where does the config file go?
.cursor/mcp.json at the root of the project. Cursor also supports a global file at ~/.cursor/mcp.json if you would rather have it everywhere.
What can it change?
Nothing, unless you grant the one write permission. It is off by default and it covers a single tool, which opens a price negotiation on your own storefront.
Does it work with Cursor's agent?
Yes. The tools are ordinary MCP tools, so the agent can chain them the same way it chains anything else.
One file. One sign-in.
Commit .cursor/mcp.json and everyone on the repository gets the same connector, each signing in as themselves.