Skip to main content

The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench • Explore Tool Discovery →

MCP Gateway

MCP Gateway
for Claude Desktop

One MCP gateway to connect Claude Desktop to 310+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.

Start Free Setup guide →
DrataGPLocalyzeFlipMindtoolsScreenloop

What is an MCP gateway?

An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple MCP servers via the open Model Context Protocol (opens in new tab). Some gateways act as proxies, routing traffic to MCP servers customers operate themselves. Others provide the underlying MCP servers as a managed service.

StackOne is the managed kind. We provide pre-built MCP servers for 310+ enterprise SaaS apps, including ones with no official MCP server today. For each app you connect, StackOne provides the MCP protocol layer, the SaaS API integration, action coverage, and the auth orchestration framework. Authentication is configured per app per organization — your team registers OAuth credentials with the SaaS provider, links them in StackOne, and end users then authorize access through that flow. Once set up, the agent reaches every connected app through one URL, with token storage, refresh, and per-user scoping handled by StackOne.

StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — bundles 310+ pre-built SaaS integrations exposing 20,000+ actions, all reachable from Claude Desktop, Claude Code, Cursor, or Goose through one URL.

Connect Claude Desktop
To All Your Apps via One MCP

Simplify your Claude Desktop MCP server setup
with the StackOne MCP gateway.

Coverage

310+ connectors.
20,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

Trust

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 Claude Desktop's context lean — only relevant actions, no raw response noise. Sharper agents, lower token costs.

Tools Discovery

Security

Agent 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 Claude Desktop
In 4 Steps

From auth config to first agent tool call in 5 minutes.

1

Edit your claude_desktop_config.json to add StackOne.

One MCP entry in claude_desktop_config.json. Restart Claude Desktop.

claude_desktop_config.json 

  "mcpServers": 
    "stackone": 
      "url": "https://api.stackone.com/mcp/{...}"
View setup guide (opens in new tab)
2

Connect each SaaS integration in StackOne.

OAuth or API key per app, done once in your dashboard. Tokens stay server-side.

salesforce
workday
hubspot
slack
zendesk
Browse all connectors
3

Scope agent actions.

Read-only, specific objects, or per-role exposure. Toggle from the StackOne dashboard.

List employees (enabled)
Get employee (enabled)
Read time-off balance (enabled)
Update profile (disabled)
Delete employee (disabled)
Agent Auth
4

Ask Claude in plain English.

StackOne maps your prompt to the right action in the right system. Done.

"Pull this week's new candidates from Ashby and welcome them in Slack."

Claude
ashby_list_candidates
Completed
slack_send_message
Completed
channel: #hiring-welcome
message: Welcome aboard, Jane Doe and 3 others! 🎉

Pulled 4 new candidates from Ashby this week and posted a welcome message to #hiring-welcome in Slack.

Anthropic Haiku 4.5

Unlock More Use Cases
with Claude Desktop

Supercharge Claude with your enterprise stack.

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.

JobAdderVincereSmartRecruitersAshbyFactorialHiBobSAP SuccessFactorsTeamtailor
Sales & CRM

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

SalesforceZoho CRMPipedriveFreshsalesHubSpotPardotCloseJustCall
Support

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

IntercomSurveyMonkeyFreshserviceServiceNowFreshdeskGorgiasDiscourseDixa
Explore more AI agent use cases

Connect any Desktop AI Agent
to the StackOne MCP Gateway

Same 310+ MCP servers. Pick your client.

Claude Code
Cursor
Goose

Frequently Asked Questions

Connecting Claude Desktop to the StackOne MCP gateway takes one entry in claude_desktop_config.json: the gateway URL plus a Base64 API key. Restart Claude Desktop and 310+ pre-built SaaS connectors are reachable through that single connection. Full walkthrough in the Claude Desktop setup guide.
An MCP gateway (also called an MCP aggregator) is a single endpoint that connects an AI agent to multiple MCP servers via the Model Context Protocol. Some gateways route traffic to MCP servers customers operate themselves; others provide the MCP servers as a managed service. StackOne is the managed kind — we provide pre-built MCP servers for 310+ enterprise SaaS apps, including ones with no official MCP server today. Authentication is configured per app per organization: your team registers OAuth credentials with the SaaS provider, links them in StackOne, and end users authorize access through that flow. Once set up, the agent reaches every connected app through one URL.
Claude Desktop can access enterprise SaaS like Salesforce, Workday, HubSpot, Greenhouse, Zendesk, NetSuite, ServiceNow, Stripe, and Notion through the StackOne MCP gateway — 310+ 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 Claude Desktop 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: 310+ 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 key (Base64-encoded in claude_desktop_config.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 Claude Desktop.

One MCP gateway, 310+ pre-built SaaS connectors. Set up in 5 minutes.

Start Free Book Demo