Cursor MCP server for Shopify inventory and cash data

Cursor can read your Keel HQ numbers from inside the editor. That's handy if you build against your own store data or want an answer without leaving your work. Add one entry to mcp.json and the tools appear.

What Cursor can read

Keel HQ serves a read-only Model Context Protocol server. These are the tools it exposes:

Two resources come with it: eos://docs/metric-calculations, which defines how each figure is calculated, and eos://reports/monthly/{year}-{month}, a published report as markdown.

These tools read your Shopify orders and products, Meta Ads campaign spend, Mercury balances and published monthly reports, all from what Keel HQ has already synced. There is no tool for Klaviyo or Google Ads data on its own.

Questions it can answer

• "How many days of cover does one of my SKUs have, and which products share that SKU across my stores?"

• "What's my cash runway, and which bills are coming up?"

• "Show Meta spend by campaign for the last three months. Was any month only partly synced?"

• "Summarize last month's published report, and tell me which figures were withheld and why."

• "Is everything you just told me current? Check the data freshness."

The questions that pay off are the ones across sources: inventory against cash, spend against revenue. Keel HQ has already joined them, and your assistant just reads the result.

Connect Cursor

1. 01Create a token

   In Keel HQ, open Settings → MCP & API tokens, and find AI assistants (MCP). Click to create a token for Cursor. It carries the read scope and expires in 90 days by default. It's shown once, so copy it before you leave the page.

2. 02Add Keel HQ to mcp.json

   Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project. Settings fills in your URL and token:

   {
     "mcpServers": {
       "keel": {
         "url": "https://app.keelhq.io/api/mcp",
         "headers": { "Authorization": "Bearer eos_YOUR_TOKEN" }
       }
     }
   }
   

   Keep the token out of any file you commit.

3. 03Test the connection

   Back in Settings → MCP & API tokens, Test connection runs the same tools/list call an assistant makes and shows the tool names it got back. Then ask a question.

Tokens, scopes and revoking

• Scope. MCP needs a token with the read scope. A token without it gets a 403, and a missing or revoked one gets a 401.

• Expiry. 30, 90 or 365 days when you create it; 90 by default.

• Revoking. Revoke the token in Settings → MCP & API tokens. The assistant loses access immediately.

• Rate limit. 120 requests a minute per token.

Your organization comes from the token, never from the request, so an assistant can only see the workspace the token was created in.

Known limits

• Read-only, by design. Cursor can't update products, record costs or send anything.

• Data is as fresh as the last sync. Shopify orders sync every six hours, so a very recent sale may not be there, and each result says so in data_freshness.

• Ad spend is by calendar month and limited to a 12-month range. There is no daily breakdown.

• Keel HQ is in private beta, with a waitlist.