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

Claude Code MCP servers

Turn Claude Code into an enterprise agent

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

DrataGPLocalyzeFlipMindtoolsScreenloop

Get Claude Code to work.
Not just chat.

One connection to StackOne, and Claude Code 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 Claude Code 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 paste into an onboarding doc. There is no OAuth app to register and no client secret to hand out. Claude Code setup guide →

Which MCP server will you
connect Claude Code 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 Claude Code?

From HR and recruiting to sales and support, Claude Code 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 Claude Code?
Your integration layer stays the same.

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

Cursor
VS Code
goose

Explore MCP clients

Frequently Asked Questions

You connect Claude Code to StackOne over MCP with one command: claude mcp add --transport http stackone https://mcp.stackone.com/mcp (add --scope user for all projects). Run /mcp, select stackone, authenticate, and choose your accounts and actions. See the setup guide.
Claude Code stores the StackOne MCP server config in .claude.json by default, scoped to the project you ran the command in — add --scope user to register it for every project instead. The entry itself is just the gateway address; your app credentials stay server-side in StackOne, never in the file.
You do not need a separate MCP server in Claude Code for each app. One stackone server covers every account you approved — Salesforce, your HRIS, your ticketing tool — through the same entry. Run /mcp again to change accounts or actions, or revoke access from Connected Apps in the StackOne dashboard.
You don't configure each app in StackOne yourself. IT connects the apps and sets the action ceiling for your project. In the consent screen you reach by authenticating from /mcp, you pick which of those accounts and actions Claude Code gets, narrowing further if you want. Rerun the flow to change it.
Once connected, Claude Code 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; claude mcp list confirms the connection. Browse the actions in the directory above.
Your app credentials — Salesforce, Workday, and the rest — live server-side in StackOne and never reach Claude Code or your machine. The gateway address carries no access on its own, so it's safe to publish internally. There's no client ID or secret to configure; each person's token is scoped to what they picked.
IT can roll out the StackOne MCP connector to a whole team in one pass: connect the apps once, and hand out a single claude mcp add --scope user command 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 Claude Code 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 the browser consent step — a CI job or headless server, for instance

Connect All Your Apps to Claude Code.

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