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 AWS Bedrock AgentCore agents

One MCP gateway to connect AWS Bedrock AgentCore to 410+ enterprise SaaS apps. No auth hassle. Token-efficient by design. Security and governance built-in.

Start Free
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 410+ 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 410+ pre-built SaaS integrations exposing 25,000+ actions, all reachable from your AgentCore agent through one URL.

Act across all your apps
from inside AWS Bedrock

One MCP gateway, every enterprise SaaS your AgentCore agent
could ever need to act on.

Coverage

410+ connectors.
25,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 AgentCore 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 the AgentCore agent
to more apps in 4 steps

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

1

Add StackOne as a Custom MCP server in AWS Bedrock AgentCore.

Open Settings → AWS Bedrock AgentCore → AI connectors, enable Custom MCP servers, then paste the StackOne gateway URL. Available immediately to every AI Agent in your workspace.

Settings → AWS Bedrock AgentCore → AI connectors

Add Custom MCP server

Display name
StackOne
Server URL
https://api.stackone.com/mcp/{...}
Authentication
API Key
Save connection
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
hubspot
workday
google-analytics
slack
Browse all connectors
3

Scope agent actions.

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

List Salesforce opps (enabled)
Get HubSpot deal (enabled)
Read Workday employee (enabled)
Modify CRM record (disabled)
Delete record (disabled)
Agent Auth
4

Ask your AgentCore agent in plain English.

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

"Pull the latest pipeline from Salesforce, grab the Q2 forecast spreadsheet from S3, and draft a board update."

AWS Bedrock
salesforce_list_opportunities
Completed
s3_get_object
Completed
bucket: forecasts-prod
key: q2-2026-board-deck.xlsx
result: 24 sheets loaded into agent context

Drafted the Q2 board update to s3://drafts/q2-board-update.md. Cross-referenced 38 Salesforce opportunities against the forecast spreadsheet.

Connect AWS Bedrock AgentCore to
any Enterprise MCP server

One MCP gateway, 410+ pre-built SaaS connectors AWS Bedrock AgentCore can act on right away.

Need another connector? Build one with the AI Connector Builder

Get your AgentCore agent
to do more across your stack

Cross-app workflows your AgentCore agent now runs in seconds instead of click-throughs.

Cross-service agent orchestration

> Read Salesforce pipeline + a Lambda function + S3 forecast in one agent flow.

SalesforceKeapZoho CRMPipedriveFreshsalesHubSpotPardotClose
Customer engagement automation

> Build a sales agent that reads HubSpot deals and drafts personalized outreach.

SalesforceKeapZoho CRMPipedriveFreshsalesHubSpotPardotClose
Internal IT & HR copilots

> Give an AgentCore agent Workday access for employee questions and HRIS lookups.

UKG ReadyWorkday (Rest and Soap)FactorialHiBobOracle Fusion HCMHumaansSAP SuccessFactorsClockify
Revenue & growth intelligence

> Pull Google Analytics campaign data into Bedrock for analysis, write back to S3.

SmartsheetTableauSurveyMonkeyMicrosoft ExcelQlikSnowflakeZoomInfoChartHop
Explore more AI agent use cases

Connect any Enterprise AI Agent
to the StackOne MCP Gateway

Same 410+ MCP servers. Same agent context. Pick yours.

Glean
Microsoft 365 Copilot
Atlassian Rovo
ServiceNow Now Assist
SAP Joule
IBM watsonx Orchestrate
Snowflake Cortex
Databricks Agent Bricks
Google Vertex AI
Intercom Fin
Zendesk
Retool Agents
Cohere North
Perplexity Comet

Frequently Asked Questions

AgentCore agents reach enterprise SaaS through an AgentCore Gateway target. Register StackOne via CLI: agentcore add gateway-target --name StackOne --type mcp-server --endpoint https://api.stackone.com/mcp --authorizer-type CUSTOM_JWT, then deploy. Same via boto3 (create_gateway_target) or AWS Console. Available immediately to your Bedrock agent, and 410+ pre-built SaaS connectors are reachable through that single target. Full walkthrough in the MCP servers as targets docs. Pay-as-you-go: $0.005 / 1,000 Gateway invocations.
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 410+ 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.
You can connect AWS Bedrock AgentCore to 410+ live MCP servers through StackOne — one managed MCP server for every enterprise app in the catalog, spanning CRM, HRIS, ATS, ticketing, finance, and more (Salesforce, Workday, Greenhouse, ServiceNow, NetSuite, HubSpot, and Zendesk among them). Each is reachable through the single gateway URL, so you add them all with one connection instead of wiring up servers app by app. Browse and search the full list in the directory on this page, or build one with the AI Connector Builder.
AWS Bedrock AgentCore exposes AWS-native services natively (S3, DynamoDB, Lambda) but has no curated MCP partner directory for operational SaaS. StackOne adds 410+ — every app reachable through one Gateway target registration instead of one per app, auth managed once in the dashboard, and tool definitions loaded only when relevant to the prompt.
Credentials sit at three layers: the StackOne MCP gateway target (OAuth credential provider registered with AgentCore Identity; AWS Secrets Manager + KMS under the hood, controlled by IAM), 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:
  • AWS-native services (S3, DynamoDB, Lambda) alone cover your agent's data needs
  • 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 AWS Bedrock.

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

Start Free Book Demo