Bridge plain-HTTP or stdio MCP clients to AWS SigV4-gated MCP endpoints (Bedrock AgentCore, API Gateway, Lambda Function URLs).
{ "mcpServers": { "aws-sigv4-mcp-proxy": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
claude mcp add aws-sigv4-mcp-proxy -- npx -y aws-sigv4-mcp-proxy@0.2.0Run in a terminal.
{ "mcpServers": { "aws-sigv4-mcp-proxy": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchTools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
Aws Sigv4 MCP Proxy runs locally over stdio.
Last checked 2026-11-11. Bridge plain-HTTP or stdio MCP clients to AWS SigV4-gated MCP endpoints (Bedrock AgentCore, API Gateway, Lambda Function URLs).
From the publisher
README is not crawled yet. Open the repository
Bridge plain-HTTP or stdio MCP clients to AWS SigV4-gated MCP endpoints (Bedrock AgentCore, API Gateway, Lambda Function URLs).