agentcore-gateway-mcp

AgentCore Gateway (MCP)

Activate this skill when an agent needs tools and you do not want to hand-roll an MCP server per integration.

When to Use

• Exposing existing Lambda functions or REST APIs to an agent as MCP tools
• Fronting an MCP server you already run
• Choosing inbound (agent → Gateway) or outbound (Gateway → target) auth
• Scaling past a few dozen tools without blowing up the context window

What It Does

Gateway converts APIs, Lambda functions, and existing services into MCP-compatible tools, and connects to pre-existing MCP servers, exposing all of them to agents through Gateway endpoints. The result is one tool surface unifying MCP servers, knowledge bases, internal APIs, and Lambda functions.

Pricing: $0.005 per 1,000 API invocations, plus $0.02 per 100 tools indexed per month.

Target Types

Target	Source of truth	Good for
Lambda	Function ARN + a tool schema you supply	Bespoke logic, private data access
OpenAPI	An OpenAPI 3 document	Existing REST services
Smithy	A Smithy model	AWS-service-shaped APIs
MCP server	A remote MCP endpoint	Servers you or a vendor already run

Lambda target sketch:

import boto3
agentcore = boto3.client("bedrock-agentcore-control")

agentcore.create_gateway_target(
    gatewayIdentifier=gateway_id,
    name="order-lookup",
    targetConfiguration={"mcp": {"lambda": {
        "lambdaArn": "arn:aws:lambda:us-east-1:123456789012:function:order-lookup",
        "toolSchema": {"inlinePayload": [{
            "name": "lookup_order",
            "description": (
                "Return status, items, and delivery estimate for a customer order. "
                "Do not use for refunds or cancellations — see process_refund."
            ),
            "inputSchema": {"type": "object",
                            "properties": {"order_id": {"type": "string"}},
                            "required": ["order_id"]},
        }]},
    }}},
    credentialProviderConfigurations=[{"credentialProviderType": "GATEWAY_IAM_ROLE"}],
)