agentcore-search-mcp

# agentcore-search-mcp An MCP server that exposes the **Amazon Bedrock AgentCore Gateway WebSearch** tool to any MCP client (Claude Code, Codex, Cursor, or your own agent). [中文文档 / Chinese documentation](README_ZH.md) · [Agent-executable install steps](INSTALL_FOR_AGENTS.md) ## What is this AgentCore Gateway already speaks MCP (JSON-RPC over HTTPS) — but it requires **AWS SigV4 request signing** (service `bedrock-agentcore`), which MCP clients cannot do themselves. This server is a local bridge: it accepts plain MCP over stdio and signs every upstream call. ``` ┌────────────────┐ stdio (MCP) ┌──────────────────────┐ SigV4-signed JSON-RPC ┌───────────────────────┐ │ MCP client │ ──────────────► │ agentcore-search-mcp │ ────────────────────────► │ AgentCore Gateway │ │ (Claude Code, │ ◄────────────── │ (this server) │ ◄──────────────────────── │ WebSearch target │ │ Codex, ...) │ └──────────────────────┘ └───────────────────────┘ └────────────────┘ ``` Exposed tool: `web_search(query, max_results=5)` → `{"results": [{"url", "title", "content", "published_date"}]}`. ## Prerequisites - **An AgentCore Gateway with a WebSearch target.** No gateway yet? Deploy one with the bundled script (see below). Or create it manually in the AWS console: Amazon Bedrock AgentCore → Gateways → create a gateway and attach the Web Search connector target, then copy the gateway's MCP endpoint URL. Note: the Web Search connector is region-limited (us-east-1 at the time of writing). - **AWS credentials** via any standard chain (environment variables, `AWS_PROFILE`, or an instance role) with permission to invoke the gateway (e.g. `bedrock-agentcore:InvokeGateway` or your account's equivalent policy for the gateway resource). - **Python ≥ 3.10** and [uv](https://docs.astral.sh/uv/) (recommended; pip also works). ### Deploy the gateway with the bundled script ```bash cd agentcore-search-mcp uv sync …