HeyMetra Cursor MCP servers for marketing and revenue data
An MCP server is a program that exposes data or actions to Cursor as a set of named tools. Cursor reads MCP servers from an `mcp.json` file — one per project under `.cursor/`, or a global one in your home directory. Once it is added, the tools appear to the model and it decides which to call — nothing is copied into Cursor and nothing about the connection leaves your account. HeyMetra is one such server: 14 marketing and revenue sources behind a single connection, 36 tools in total (30 read, 6 write), of which 7 sources work today and 7 do not yet.
Adding one in Cursor
-
Authorise the accounts you want reachable. This happens once, in HeyMetra, and is the part that is the same whichever client you use.
-
Add the server in Cursor. Cursor reads MCP servers from an `mcp.json` file — one per project under `.cursor/`, or a global one in your home directory.
-
Ask Cursor something that needs one of the accounts. The model picks the tool; you never name it.
Client interfaces move, and this one has moved before. Where a step here disagrees with what is on your screen, trust the screen — and tell us, so the page stops being wrong for the next person.
What you can connect today
Only what works now. Connectors still being built are on the connectors page, marked Soon, and they are deliberately not in this table.
| Account | Category | Access |
|---|---|---|
| Google Search Console tools | Analytics | read |
| Trendyol tools | Ecommerce | read |
| WooCommerce tools | Ecommerce | read |
| Zoho CRM tools | Revenue & CRM | read |
| AppsFlyer tools | Mobile | read |
| Adapty tools | Mobile | read |
| App Store Connect tools | Mobile | read |
Why one server rather than four
You can add several MCP servers to Cursor at once, and for separate questions that works. It stops working when one question needs two of them: Cursor has to call each in turn and reconcile the results itself, from whatever fits in its context, without knowing that one account's "conversion" and another's "purchase" are the same event. Holding the accounts behind one server moves that work to where the definitions are known.
Frequently asked
Does Cursor support MCP?
Yes. Cursor reads MCP servers from an `mcp.json` file — one per project under `.cursor/`, or a global one in your home directory.
What can I connect Cursor to for marketing data?
Any MCP server covering the account you care about. Most vendors now publish one for their own product; the difference between those and HeyMetra is how many accounts a single server can see — one, versus 14.
Is a remote MCP server different from a local one?
Yes. A local one runs as a process on your own machine and stops when you close the client. A remote one runs on the operator’s infrastructure and is reached over HTTP, so there is nothing to install and nothing to keep running — and the credentials live with the operator.
Can a MCP server change my ad account?
Only if it exposes tools that write. In HeyMetra, 6 of 36 tools do, all of them on advertising campaigns and budgets, and each call is checked against ceilings held in code before anyone is asked to approve it.
The other clients
Use it from the Cursor subscription you already pay for
There is no second model to buy here. The reasoning happens in your client; HeyMetra supplies the accounts and the bounds on what a tool may do with them.