Skip to main content The #1 agentic semantic tool search: 91.6% first-try accuracy on S1 Search Bench Explore Tool Discovery
StackOne
Connectors
Pricing
Login
Book Demo Start Free
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

Explore More Use-Cases
Next up: Meet us at Glean:GO 2026
StackOne
Connectors
Connect

Connect to everything your agents need, without writing the infrastructure to get there.

Secure

Enterprise-grade controls to ensure your agent always meets security & compliance standards.

Optimize

Maximise agent efficiency – faster responses, increased accuracy, fewer tokens used.

Use-Cases
Pricing
Book Demo Start Free

AWS Bedrock AgentCore MCP Gateway

Turn AWS Bedrock AgentCore into an enterprise agent

Let your employees delegate real work to AWS Bedrock AgentCore across all their apps, under their own identity and permissions.

Book a Demo Start Free
DrataGPLocalyzeFlipMindtoolsScreenloop

Get AWS Bedrock AgentCore to work.
Not just chat.

One connection to StackOne, and AWS Bedrock AgentCore 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 470+ managed MCP servers and 28,000+ tested tools. No auth code to write, no API maintenance.

Browse all connectors

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 and boost reliability with the Falcon execution engine. Pre-synced data for faster context is coming soon.

Tool discovery Falcon

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)
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, 450+ 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 CRMPipedriveFreshsalesJustCallPardotAircall
Customer engagement automation

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

SalesforceKeapZoho CRMPipedriveFreshsalesJustCallPardotAircall
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

Not everyone on AWS Bedrock?
Your integration layer stays the same.

The same setup works across AI cloud platforms like watsonx Orchestrate, Retool Agents, and every other MCP client.

watsonx Orchestrate
Retool Agents
Databricks

Explore MCP clients

Frequently Asked Questions

You connect AWS Bedrock AgentCore to the StackOne MCP gateway via an AgentCore Gateway target: register StackOne with agentcore add gateway-target --name StackOne --type mcp-server --endpoint https://api.stackone.com/mcp --authorizer-type CUSTOM_JWT (or boto3/Console), then deploy. See the MCP servers as targets docs. Pay-as-you-go: $0.005/1,000 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, like StackOne, provide the MCP servers as a managed service — pre-built for 470+ enterprise SaaS apps, including ones with no official MCP server today.
You can connect AWS Bedrock AgentCore to 470+ live MCP servers through StackOne, spanning CRM, HRIS, ATS, ticketing, and finance — Salesforce, Workday, Greenhouse, and more. Each is reachable through one gateway URL instead of wiring up servers app by app. Browse the full list in the directory on this page, or build your own.
AWS Bedrock AgentCore exposes AWS-native services natively (S3, DynamoDB, Lambda) but has no curated MCP partner directory for operational SaaS. StackOne adds 470+ — 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 tokens scoped to what each person authorized.
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 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
  • Your provider already does tool discovery and server-side execution

Connect All Your Apps to AWS Bedrock.

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

Start Free Book Demo