Connect
Optimize
Secure
MCP servers for AWS Bedrock AgentCore
MCP Servers
for AWS Bedrock AgentCore agents
Let your AgentCore agent act across 270+ enterprise SaaS — without leaving AWS Bedrock. No auth hassle. Token-efficient by design. Security and governance built-in.
What is an MCP gateway?
MCP gateways are real-time integration infrastructure connecting AI
agents to the SaaS apps they need to use. They expose one MCP server
instead of many to the AI agent. They are built on the open Model Context Protocol (opens in new tab), and
are also called MCP aggregators.
MCP gateways use whatever communication protocol each MCP server requires
(stdio, SSE, streamable HTTP), maximize the action coverage agents can
call, and handle authentication, agent action scoping, tool-call
optimization, agent security, and tool-call observability.
StackOne's MCP gateway — SOC2, HIPAA, CCPA, and GDPR compliant — brings this infrastructure to 270+ pre-built SaaS integrations exposing 18,000+ actions, 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
270+ connectors.
18,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
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 Salesforce opps (enabled)
Get HubSpot deal (enabled)
Read Workday employee (enabled)
Modify CRM record (disabled)
Delete record (disabled)
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.
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.
Customer engagement automation
> Build a sales agent that reads HubSpot deals and drafts personalized outreach.
Internal IT & HR copilots
> Give an AgentCore agent Workday access for employee questions and HRIS lookups.
Revenue & growth intelligence
> Pull Google Analytics campaign data into Bedrock for analysis, write back to S3.
Connect any Enterprise AI Agent
to the StackOne MCP Gateway
Same 270+ MCP servers. Same agent context. Pick yours.
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 270+ 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 is real-time integration infrastructure connecting AI agents to the SaaS apps they need to use. It exposes one MCP server instead of many to the AI agent, and handles authentication, agent action scoping, tool-call optimization, agent security, and tool-call observability. Also called an MCP aggregator.
Your AgentCore-built agents can access enterprise SaaS like Salesforce, HubSpot, Workday, Linear, Slack, Greenhouse, Stripe, NetSuite, and Google Analytics through the StackOne MCP gateway — categories that complement AWS's native services (Lambda, S3, DynamoDB) and Bedrock's named partners (GitHub, Salesforce, Slack, Jira, Asana, Zendesk). 270+ pre-built connectors total. New connectors ship continuously, and you can build custom ones with AI Integration Builder. See all connectors.
AWS Bedrock AgentCore exposes AWS-native services natively (S3, DynamoDB, Lambda) but has no curated MCP partner directory for operational SaaS. StackOne adds 270+ — 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, 270+ pre-built SaaS connectors. Set up in 5 minutes.