Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no 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.
AbrirAn MCP (Model Context Protocol) server that acts as a transparent proxy, forwarding MCP protocol messages to a target MCP server that requires IAM authentication. The proxy automatically signs requests with AWS Signature Version 4 (SigV4) or Signature Version 4A (SigV4a).
This proxy enables MCP clients to connect to IAM-authenticated MCP servers without implementing signing logic themselves. It sits between the client and the target server, transparently forwarding messages while adding AWS authentication.
┌─────────────┐ ┌──────────────────────────┐ ┌─────────────────┐
│ │ stdio │ │ HTTPS │ │
│ MCP Client │────────▶│ Signing Proxy │────────▶│ Target MCP │
│ │ │ (mcp.Server) │ +SigV4 │ Server (IAM) │
│ │◀────────│ │◀────────│ │
└─────────────┘ └──────────────────────────┘ └─────────────────┘
git clone https://github.com/nisimpson/mcp-sigv4-proxy.git
cd mcp-sigv4-proxy
go build -o sigv4-proxy ./sigv4-proxy
go install github.com/nisimpson/mcp-sigv4-proxy@latest
Set up AWS credentials (see AWS Credentials section)
Configure the proxy using environment variables:
export MCP_TARGET_URL=https://your-mcp-server.execute-api.us-east-1.amazonaws.com
export AWS_REGION=us-east-1
export AWS_SERVICE_NAME=execute-api
sigv4-proxy
The proxy will start and listen for MCP protocol messages on stdin/stdout.
The proxy can be configured via command-line flags or environment variables. Command-line flags take precedence over environment variables.
sigv4-proxy \
--target-url https://abc123.execute-api.us-east-1.amazonaws.com \
--region us-east-1 \
--service-name execute-api
export MCP_TARGET_URL=https://abc123.execute-api.us-west-2.amazonaws.com
export AWS_REGION=us-west-2
export AWS_SERVICE_NAME=execute-api
export AWS_SIG_VERSION=v4
sigv4-proxy
sigv4-proxy \
--target-url https://global-mcp-server.example.com \
--region us-east-1 \
--service-name execute-api \
--sig-version v4a
sigv4-proxy \
--target-url https://abc123.execute-api.us-east-1.amazonaws.com \
--region us-east-1 \
--service-name execute-api \
--profile production
sigv4-proxy \
--target-url https://abc123.execute-api.us-east-1.amazonaws.com \
--region us-east-1 \
--service-name execute-api \
--sse \
--timeout 30s
sigv4-proxy \
--target-url https://abc123.execute-api.us-east-1.amazonaws.com \
--region us-east-1 \
--service-name execute-api \
--headers "X-Custom-Header=value,X-API-Version=v2"
See docs/examples.md for more detailed configuration examples.
The proxy uses the standard AWS SDK credential chain to load credentials. Credentials are loaded in the following order:
Environment Variables
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKEN (optional, for temporary credentials)Shared Credentials File (~/.aws/credentials)
--profile or AWS_PROFILEIAM Role (when running on AWS infrastructure)
export AWS_ACCESS_KEY_ID=AKIAIOSFODNN7EXAMPLE
export AWS_SECRET_ACCESS_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
export AWS_SESSION_TOKEN=AQoDYXdzEJr... # Optional, for temporary credentials
Create or edit ~/.aws/credentials:
[default]
aws_access_key_id = AKIAIOSFODNN7EXAMPLE
aws_secret_access_key = wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
[production]
aws_access_key_id = AKIAI44QH8DHBEXAMPLE
aws_secret_access_key = je7MtGbClwBF/2Zp9Utk/h3yCo8nvbEXAMPLEKEY
Then use the profile:
sigv4-proxy --profile production ...
When running on AWS infrastructure (EC2, ECS, Lambda), the proxy will automatically use the IAM role attached to the instance/task/function. No additional configuration is needed.
For more details, see docs/aws-credentials.md.
Add the proxy to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"iam-protected-server": {
"command": "/path/to/sigv4-proxy",
"args": [
"--target-url", "https://abc123.execute-api.us-east-1.amazonaws.com",
"--region", "us-east-1",
"--service-name", "execute-api"
]
}
}
}
The proxy communicates via stdio, so it can be used with any MCP client that supports stdio transport. Configure your client to launch the proxy as a subprocess and communicate via stdin/stdout.
Cause: The target URL was not provided.
Solution: Set MCP_TARGET_URL environment variable or use --target-url flag.
Cause: AWS credentials are not configured or not accessible.
Solution:
~/.aws/credentials, or IAM role--profileCause: The target URL is malformed or uses an unsupported protocol.
Solution: Ensure the target URL starts with https:// (or http:// for local testing).
Cause: An invalid signature version was specified.
Solution: Use either v4 or v4a for the --sig-version flag or AWS_SIG_VERSION environment variable.
For more troubleshooting tips, see docs/troubleshooting.md.
MIT License - see LICENSE file for details.
Contributions are welcome! Please see CONTRIBUTING.md for development setup, testing guidelines, and how to submit pull requests.
For issues, questions, or contributions, please visit the GitHub repository.
An MCP proxy for servers that require AWS sigv4 or sigv4a authentication.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
MCP Sigv4 Proxy roda localmente via stdio.
Última verificação: 2026-10-28. An MCP proxy for servers that require AWS sigv4 or sigv4a authentication.