Connect
Optimize
Secure
MCP Gateway
MCP Gateway
for IBM watsonx Orchestrate
One MCP gateway to connect watsonx Orchestrate to 310+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.
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 your watsonx Orchestrate agent through one URL.
Act across all your apps
from inside watsonx Orchestrate
One MCP gateway, every enterprise SaaS your watsonx Orchestrate
agent could ever need to act on.
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 the watsonx Orchestrate agent'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 watsonx Orchestrate
to more apps in 4 steps
From auth config to first agent tool call in 5 minutes.
1
Register StackOne as an MCP toolkit in watsonx Orchestrate.
Your platform admin runs one ADK command to register the StackOne gateway, then every Agent Builder in your workspace can pick it from Toolset → Add tool → Import from MCP server.
Build → Agent Builder → Toolset → Add tool
Import from MCP server
Toolkit name
StackOne
MCP server URL
https://api.stackone.com/mcp/{...}
Transport
streamable-http
Credentials
Team credentials
Save toolkit
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 tools (enabled)
Get tool (enabled)
Run action (enabled)
Configure tool (disabled)
Remove tool (disabled)
4
Ask your watsonx Orchestrate agent in plain English.
StackOne maps your prompt to the right action in the right system. Done.
"Pull open Workday reqs against the Q3 hiring plan and draft an onboarding brief in Agent Builder."
workday_list_open_positions
Completed
greenhouse_list_candidates
Completed
stage: offer extended
department: Engineering, Sales
result: 12 candidates ready
Matched 12 Greenhouse offers to 14 open Workday reqs. Drafted the Q3 Onboarding Brief in Agent Builder.
Get watsonx Orchestrate
to do more across your stack
Cross-app workflows your watsonx Orchestrate agent now runs in seconds instead of click-throughs.
Talent & Recruiting
> Pull every open Greenhouse requisition and draft an offer-letter pack in Agent Builder.
Customer Support
> Triage this week's Zendesk escalations and update the customer-success playbook.
Dev & Engineering Workflow
> Pull this sprint's GitHub open PRs and log the merge-blocker list in Agent Builder.
Sales & Pipeline Ops
> Sync HubSpot deal stages into your Agent Builder pipeline review.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 310+ MCP servers. Same agent context. Pick yours.
Frequently Asked Questions
watsonx Orchestrate consumes external MCP servers as a client. Your platform admin registers the StackOne gateway once via the watsonx Orchestrate ADK (
orchestrate toolkits import --kind mcp --url ... --transport streamable-http), and the toolkit then appears in Agent Builder. From there, open Build → Agent Builder → your agent → Toolset → Add tool → Add from file or MCP server → Import from MCP server, pick the StackOne toolkit, and configure credentials (Member or Team). 310+ pre-built SaaS connectors are reachable through that single toolkit. Full walkthrough in the IBM Importing tools from an MCP server docs.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.
watsonx Orchestrate can access enterprise SaaS like Workday, Greenhouse, HubSpot, Zendesk, GitHub, Linear, Jira, Intercom, and BambooHR 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.
watsonx Orchestrate's Agent Catalog ships 7 named partner agents (Box, Mastercard, Oracle, Salesforce, ServiceNow, Symplistic.ai, 11x) plus enterprise app integrations (Workday, SAP, Microsoft Dynamics). StackOne adds the other 310+ — every app reachable through one ADK toolkit registration instead of N separate ones, 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 passed to
orchestrate toolkits import, stored as Team or Member credentials in watsonx Orchestrate), 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:
- IBM's Agent Catalog partners (Box, Mastercard, Oracle, Salesforce, ServiceNow, Symplistic.ai, 11x) already cover your apps
- 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 watsonx Orchestrate.
One MCP gateway, 310+ pre-built SaaS connectors. Set up in 5 minutes.