Skip to main content
Amazon Bedrock AgentCore Gateway treats remote MCP servers as first-class targets. Consensus’s stateless server works with all supported protocol versions, including the sessionless 2026-07-28.

Shared API key

1

Store the key

2

Create the target

Or with the toolkit CLI: agentcore add gateway-target --name Consensus --type mcp-server --endpoint https://mcp.consensus.app/mcp --gateway MyGateway, then agentcore deploy.

Per-user OAuth

AgentCore’s OAuth credential providers require a clientId and clientSecret; they don’t perform Dynamic Client Registration. Contact sales for a confidential client, then create a CustomOAuth2 provider with discoveryUrl set to https://consensus.app/.well-known/oauth-authorization-server and use grantType: AUTHORIZATION_CODE on the target. The target stays in CREATE_PENDING_AUTH until an admin completes consent.

Notes

  • The credential provider must be in the same region as the gateway.
  • Tool schemas are synced at create time; call SynchronizeGatewayTargets if the tool list changes.
  • Token passthrough (JWT_PASSTHROUGH) isn’t available for MCP targets.
AWS docs: MCP server targets · Outbound auth