# AWS Bedrock AgentCore

AWS Bedrock AgentCore is an MCP server that connects AI agents to Amazon Bedrock AgentCore APIs for runtime, memory, identity, gateway, and policy operations through 122 tools.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 9939 repo stars
- Author: awslabs
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/awslabs/mcp/tree/HEAD/src/amazon-bedrock-agentcore-mcp-server
- Updated: 2026-10-23
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/mcp/aws-bedrock-agentcore

## What it does

The server exposes seven AgentCore primitives: Runtime (14 tools) deploys agent runtimes and endpoints, Memory (21) handles events and semantic search, Identity (21) manages OAuth2 providers and token vaults, Gateway (15) creates API gateways and resource policies, Policy (15) operates policy engines, Browser (25) automates cloud-based browsing, Code Interpreter (10) runs sandboxed code execution. Documentation tools (`search_agentcore_docs`, `fetch_agentcore_doc`) work independently.

Calls real boto3 APIs. Requires configured AWS credentials (`AWS_PROFILE`, `AWS_ACCESS_KEY_ID`, or IAM role) and Python 3.10+. Without credentials, resource creation and management tools will not start.

All primitives are enabled by default. `AGENTCORE_DISABLE_TOOLS` turns off specific ones (e.g., `browser,code_interpreter`), `AGENTCORE_ENABLE_TOOLS` registers only the listed primitives. Documentation tools remain available regardless.

## Requirements
- Needs: Docker
- Works with: AWS

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- deploy an agent runtime in AgentCore from Claude Code
- store an event in agent memory and run semantic search
- configure an OAuth2 identity provider and issue API keys
- create an API gateway and attach a resource policy
- execute code in a sandboxed environment with file upload

## Example prompts
- Create an agent runtime in `us-east-1` with default settings
- Store this event in memory with tags `user-feedback` and `bug-report`
- Search AgentCore docs for gateway access policy configuration

## Similar
- [amazon-bedrock](https://affpapa.org/en/nevibecode/skills/amazon-bedrock.md) — skill · 9500 installs
- [aws-strands-agents-agentcore](https://affpapa.org/en/nevibecode/skills/aws-strands-agents-agentcore.md) — skill · ★ 173 repo stars
- [aws-agentic-ai](https://affpapa.org/en/nevibecode/skills/aws-agentic-ai.md) — skill · 702 installs
- [aws-sdk-java-v2-bedrock](https://affpapa.org/en/nevibecode/skills/aws-sdk-java-v2-bedrock.md) — skill · 3900 installs
- [aws-agents](https://affpapa.org/en/nevibecode/plugins/aws-agents.md) — plugin · ★ 3536 repo stars
- [aws-harness](https://affpapa.org/en/nevibecode/skills/aws-harness.md) — skill · ★ 301 repo stars

From the same set: [awslabs/mcp](https://affpapa.org/en/nevibecode/by/awslabs/mcp.md) — 36 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
