Cursor MCP servers for business tools

Add one url to mcp.json and sign in. Cursor's agent can then read real orders, payments, tickets and analytics while it works in your project. No API keys, and no server to run.

https://app.popmcp.com/mcp

Connect PopMCP to Cursor See the setup steps

Steps checked against Anysphere's documentation on 30 October 2026

Connect Cursor to PopMCP

Add the URL to mcp.json once, for every project or for one, then sign in from Customize.

Add PopMCP to Cursor

A remote server needs only its url. Cursor registers itself with PopMCP when you sign in, so there is no client ID or secret to paste.

Sign in at app.popmcp.com, connect Shopify, Stripe or any other tool, and check each one shows as Verified.
Add popmcp to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in one project. A remote server needs only its url.
mcp.json
```
{
  "mcpServers": {
    "popmcp": { "url": "https://app.popmcp.com/mcp" }
  }
}
```
Open Customize in Cursor's sidebar, click MCPs, find popmcp and follow the authentication prompts. Cursor registers itself with PopMCP automatically; there is no client secret.
On the PopMCP consent screen, tick only the connectors Cursor should reach, then approve.
Cursor asks for approval before it uses an MCP tool by default. Ask the agent to run list_connections, then start with a read-only request.

What you save and run, in order. Drawn from the steps beside it, not a screenshot.

Cursor docs: Model Context Protocol

The short answer

Cursor supports the Model Context Protocol (MCP) over Streamable HTTP and SSE with OAuth: you add a remote server's url to mcp.json, sign in from Customize, then MCPs, and Cursor's agent can call that server's tools. PopMCP is a hosted MCP server that puts 100+ business tools behind one URL, https://app.popmcp.com/mcp, so one entry reaches every tool you connect in PopMCP. Cursor asks for approval before it uses an MCP tool by default.

What to ask Cursor

Cursor calls PopMCP's tools, PopMCP reads your connected accounts, and the answer comes back in the chat. The tool names are the real ones Cursor calls.

CursorPopMCP connected

Pull three recent Shopify orders so I can see the real field shapes before I write the parser.

PopMCP, 1 tool call

shopify_get_ordersThe three most recent orders, with line itemsread

Ask Cursor about your tools

The reply is drawn as bars on purpose: the figures come from your own accounts, so this page does not make any up.

More to paste into Cursor

Pull three recent Shopify orders so I can see the real field shapes.
Which Stripe products referenced in this project no longer exist?
List the HubSpot deal properties we use, so I can type them.

PopMCP's consent screen. Tick only the connections Cursor should reach, then Authorize. Drawn from PopMCP's own consent screen, not a screenshot. Your layout may differ.

You decide what Cursor can reach

That is set in PopMCP, not in Cursor. The sign-in ends on a consent screen that lists your connections.

OAuth sign-in, no API keys: Cursor signs in to PopMCP with OAuth 2.1. There is nothing to paste, and your Shopify or Stripe credentials stay encrypted inside PopMCP.
You pick the connectors: The consent screen lists your connections. Cursor reaches only the ones you tick.
Read-only where you want it: A workspace owner or admin sets each teammate to no access, read, or read and write, per connection.
Every call is on the record: Usage shows each request by user, connector and tool. Removing someone's access applies on the next request.

Where PopMCP works in Cursor

Each row is one place Cursor runs, and what its vendor says about adding a remote MCP server there.

Where	Remote MCP	How it signs in
Every project~/.cursor/mcp.json	Supported	OAuth sign-in, with dynamic client registration
One project.cursor/mcp.json in the repository	Supported	Each person signs in with their own PopMCP account

Before you connect Cursor

What Cursor's docs say about remote servers, and one caution of ours.

Approval before tools: Cursor asks for approval before it uses an MCP tool by default. The approval settings change that; leave it on until you trust what the agent asks for.
Global or per project: ~/.cursor/mcp.json applies to every project; .cursor/mcp.json applies to one, and can be committed so the team gets the same entry.
Admin controls are Enterprise: Cursor names no plan requirement for adding a server. Its Enterprise plan adds controls over which MCP servers people may use.
Data ends up in files: Cursor's agent can write what it reads into files in your project. Keep live customer data out of commits.

Questions about Cursor and PopMCP

Answered from Anysphere's documentation, checked on 30 October 2026.

How do I add a remote MCP server to Cursor?

Add "popmcp": { "url": "https://app.popmcp.com/mcp" } under mcpServers in ~/.cursor/mcp.json, or in .cursor/mcp.json for one project. Then open Customize, click MCPs and follow the sign-in prompts.

Does Cursor support OAuth for MCP servers?

Yes, for remote servers over Streamable HTTP and SSE. Cursor registers itself as a public client with no secret, so PopMCP needs nothing pasted.

Which Cursor plan do I need?

Cursor's MCP pages name no plan requirement for adding a remote server. Its Enterprise plan adds admin controls over which MCP servers people may use.

Will Cursor change data in my tools without asking?

Cursor asks before it uses an MCP tool by default. In PopMCP, Free is read-only, a new connection on a paid plan starts read-only until an owner or admin turns on write actions, and each teammate is set to no access, read, or read and write.

Can my team share the PopMCP entry?

Commit .cursor/mcp.json with the popmcp entry. Each person still signs in with their own PopMCP account, so each gets the access their workspace allows.

Sources

3 references, checked 30 October 2026

Every step on this page comes from these sources. Community sources are labelled, and we used them only where the vendor has not documented a step.

Cursor docs: Model Context ProtocolTransports (stdio, SSE, Streamable HTTP), OAuth with dynamic client registration for remote servers, and approval before MCP tools by default.cursor.com
Cursor help: MCP serversThe mcp.json locations and shape, and the Customize, then MCPs screen where servers are managed and signed in.cursor.com
Cursor: PricingMCP access controls are listed on the Enterprise plan.cursor.com