Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery

Cursor MCP servers

Turn Cursor into an enterprise agent

Let your employees delegate real work to Cursor across all their apps, under their own identity and permissions.

DrataGPLocalyzeFlipMindtoolsScreenloop

Get Cursor to work.
Not just chat.

One connection to StackOne, and Cursor gets scoped access to every app your employees use, to act on their behalf.

Connect

Make every system AI-ready

Give your AI access to 450+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Secure

Keep AI under control

Enforce identity-based access, screen every response for prompt injection, and audit every action.

Optimize

Trust what AI delivers

Keep your agent sharp with lean tool loading, boost reliability with the Falcon execution engine, and enhance its context with pre-synced data.

Roll out MCP tools to every Cursor user.
Set up and onboarding in minutes.

One-time setup for IT. Self-serve for everyone else.

IT Admin

One-time setup, no per-user wiring.

The URL carries no access on its own, so it is safe to publish in an internal wiki or commit with the repo. There is no wrapper package to install and no client secret to hand out. Cursor setup guide →

Which MCP server will you
connect Cursor to?

Connect to the StackOne MCP gateway once and give your employees' agents instant access to 450+ pre-built SaaS connectors and 28,000+ MCP tools.

Need another connector? Build one with the AI Connector Builder

What will your employees
delegate to Cursor?

From HR and recruiting to sales and support, Cursor completes work across any app you connect.

HR & People Ops

> List this month's Workday work anniversaries and draft a personalized celebration message for each.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Recruiting

> Compare Greenhouse interview feedback across stages and flag candidates trending toward an offer.

JobAdderVincereSmartRecruitersAshbyManatalFactorialHiBobSAP SuccessFactors
Sales & CRM

> Analyze Salesforce deals stuck 30+ days and draft a re-engagement email for each owner.

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
Support

> Cluster yesterday's Zendesk tickets by theme and surface the top 3 trending issues.

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa

Not everyone on Cursor?
Your integration layer stays the same.

The same setup works across Coding agents like VS Code, goose, and every other MCP client.

VS Code
goose
Codex

Explore MCP clients

Frequently Asked Questions

You connect Cursor to StackOne over MCP with one config entry: add an mcpServers block to ~/.cursor/mcp.json (or .cursor/mcp.json for one project), naming the server stackone with "url" set to https://mcp.stackone.com/mcp. Or use Settings → MCP → Add new MCP server. Sign in, pick your project, choose accounts and actions, and authorize. Setup guide.
Cursor stores the StackOne MCP server config in ~/.cursor/mcp.json globally, or .cursor/mcp.json at a project root to scope it to one repo. Both use the same mcpServers entry with a "url" key, not the httpUrl other clients use. Since it's a plain file, the project version can be committed with the repo — it holds only the gateway address, never credentials.
You do not need to install anything else to use MCP servers in Cursor. It connects to remote Streamable HTTP servers directly and runs the OAuth flow itself — no wrapper package, no local proxy, no gateway to stand up. The whole client side is the mcpServers entry pointing at https://mcp.stackone.com/mcp.
You don't configure each app in StackOne yourself. IT connects the apps and sets the action ceiling for your project. Cursor sends you to a consent screen where you pick which of those accounts and actions to use, narrowing further if you want. Rerun the flow to change it.
Once connected, Cursor can run whatever actions you granted, across 450+ live connectors and 28,000+ tested actions — CRM, HRIS, ATS, ticketing, finance, and more. Tools go live as soon as you authorize, and Settings → MCP shows StackOne with a green dot. Browse the actions in the directory above.
Your app credentials — Linear, Salesforce, and the rest — live server-side in StackOne and never reach Cursor or your machine. The gateway address in mcp.json carries no access on its own, so it's safe to commit with the repo. There's no client ID or secret in that file; Cursor registers itself during the OAuth handshake.
IT can roll out the StackOne MCP connector to a whole team in one pass: connect the apps once, and commit a single .cursor/mcp.json to the repo instead of briefing people individually. Each person still signs in, picks their own accounts and actions, and authorizes — so nobody exceeds the ceiling IT set.
Skip connecting Cursor to StackOne when any of these is true:
  • An existing first-party MCP server already covers your apps
  • You use only a handful of actions across a few apps
  • You don't need multi-tenancy or per-action scoping
  • Prompt injection isn't a concern
  • Nobody can complete a browser consent step — a CI job or headless server, for instance

Connect All Your Apps to Cursor.

One URL, 450+ pre-built SaaS connectors. Set up in minutes.