Connect
Optimize
Secure
MCP servers for Cursor
The MCP Gateway
for Cursor
Give your Cursor agent access to 270+ managed MCP servers. No auth hassle. Token-efficient by design. Security and governance built-in.
What is an MCP gateway?
MCP gateways are real-time integration infrastructure connecting AI
agents to the SaaS apps they need to use. They expose one MCP server
instead of many to the AI agent. They are built on the open Model Context Protocol (opens in new tab), and
are also called MCP aggregators.
MCP gateways use whatever communication protocol each MCP server requires
(stdio, SSE, streamable HTTP), maximize the action coverage agents can
call, and handle authentication, agent action scoping, tool-call
optimization, agent security, and tool-call observability.
StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — brings this infrastructure to 270+ pre-built SaaS integrations exposing 18,000+ actions, reachable from Cursor, Claude Desktop, Claude Code, or Goose through one URL.
Connect Cursor
To All Your Apps via One MCP
Simplify your Cursor MCP server setup
with the StackOne MCP gateway.
Coverage
270+ connectors.
18,000+ tested actions.
Every action is built and maintained by StackOne, tested against the live API, and updated when vendors change their endpoints.
Browse all connectors →
Auth & Governance
Auth & governance,
simplified.
StackOne handles OAuth, API keys, refresh, and scopes for every connector, giving enterprise IT full control through auth configs in a multi-tenant setup.
Agent Auth →
Performance
Agent context window,
managed.
Tool Discovery and Code Mode keep Cursor's context lean — only relevant actions, no raw response noise. Sharper agents, lower token costs.
Tools Discovery →
Agent Security
Security,
built in.
Defender scans every MCP tool response for prompt injection in real time. Up to 97.44%¹ detection, 0.2% false positives. SOC2, HIPAA, CCPA, GDPR compliant.
Prompt Injection Defense →¹ Jayavibhav test, 65,000 samples.
Connect Cursor
In 4 Steps
From auth config to first agent tool call in 5 minutes.
1
Edit your .cursor/mcp.json to add StackOne.
One MCP entry in .cursor/mcp.json. Restart Cursor.
.cursor/mcp.json
"mcpServers": "stackone": "url": "https://api.stackone.com/mcp/{...}"
2
Connect each SaaS integration in StackOne.
OAuth or API key per app, done once in your dashboard. Tokens stay server-side.
3
Scope agent actions.
Read-only, specific objects, or per-role exposure. Toggle from the StackOne dashboard.
List issues (enabled)
Get issue (enabled)
Comment on issue (enabled)
Close issue (disabled)
Delete issue (disabled)
4
Ask Cursor agent in plain English.
StackOne maps your prompt to the right action in the right system. Done.
"Find Linear tickets blocked over a week and post a summary in #engineering."
Cursor linear_list_issues
Completed
slack_send_message
Completed
channel: #engineering
message: 4 tickets blocked > 7 days. Top: ENG-241 (waiting on design), ENG-198 (API spec).
Found 4 Linear tickets blocked over a week and posted a summary to #engineering in Slack.
Anthropic Haiku 4.5
Unlock More Use Cases
with Cursor
Supercharge Cursor agent with your enterprise stack.
HR & People Ops View →
> Pull this week's new hires from BambooHR and post a welcome thread in #all-hands on Slack.
Recruiting View →
> List Ashby candidates who passed the tech screen and create their interview calendar invites.
Sales & CRM View →
> Find HubSpot deals closing this week and post a digest with talking points in #revenue on Slack.
Connect StackOne MCP Gateway
to Any AI Agent.
Same 270+ MCP servers. Pick your client.
Frequently Asked Questions
Connecting Cursor to the StackOne MCP gateway takes one entry in
.cursor/mcp.json: paste the gateway URL with your account ID and token as query parameters. Restart Cursor and 270+ pre-built SaaS connectors are reachable through that single connection. Full walkthrough in the Cursor MCP setup guide.An MCP gateway is real-time integration infrastructure connecting AI agents to the SaaS apps they need to use. It exposes one MCP server instead of many to the AI agent, and handles authentication, agent action scoping, tool-call optimization, agent security, and tool-call observability. Also called an MCP aggregator.
Cursor agent can access enterprise SaaS like Salesforce, Workday, HubSpot, Greenhouse, Zendesk, NetSuite, ServiceNow, Stripe, and Notion through the StackOne MCP gateway — 270+ pre-built connectors in total. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
You'd connect Cursor to one MCP server per app — each with its own setup, its own auth flow, and its own tool definitions sitting in your context. StackOne replaces those N connections with one gateway URL: 270+ apps reachable through a single connection, auth managed once in the dashboard, and tool definitions loaded only when relevant to the prompt.
Credentials sit at three layers: your StackOne API token (embedded in the gateway URL inside
.cursor/mcp.json on your machine), SaaS connector credentials (server-side in your StackOne dashboard), and per-user OAuth or session tokens (server-side, scoped per user). StackOne stores OAuth tokens and API keys, refreshes them automatically, and only exposes the actions you've authorized to the agent.Skip the StackOne MCP gateway when any of these is true:
- An existing first-party or third-party MCP server covers your apps, no tool extension needed
- You only use a handful of actions across a few apps
- You don't need multi-tenancy, per-user permissions, or per-action scoping
- Indirect prompt injection isn't a concern
- Your MCP provider already does tool discovery and server-side execution to keep the agent context lean
Connect All Your Apps to Cursor.
One MCP gateway, 270+ pre-built SaaS connectors. Set up in 5 minutes.