Solutions

Connect AWS MCP — no proxy required.

AWS-hosted MCP servers expect AWS SigV4-signed requests. Meandr signs them for you, so you point it at the server and it just works — no proxy or sidecar for you to stand up and babysit.

Try for free See how it works

Add an AWS server like any other.

Paste the server's address and Meandr handles the AWS SigV4 signing behind it — there's nothing extra to stand up, and no proxy to keep alive.

  1. 01 Add

    Add the server and turn on AWS MCP SigV4 signing

    Open Servers, click Add MCP server and paste the AWS MCP server's address. Pick AWS · SigV4, set the service and region, then paste the access key ID and secret access key from AWS.

    • Nine sign-in methods in one list, from None to AWS · SigV4
    • Your agents keep only their Meandr key and never see the AWS one
    • Meandr signs every request, so there's no mcp-proxy-for-aws to run, as AWS SigV4 without a proxy explains
    Connect a server, step by step
    Point Meandr at the server — the signing is already handled.

  2. 02 Tools

    The AWS tools appear in your catalog

    After saving, Meandr reads the server's tools and you choose which ones your agents can use.

    • Read-only and destructive tools are marked
    • Leave a destructive tool off, and no agent can call it
    Give each agent only the tools it needs

  3. 03 Use

    Your agent calls AWS through Meandr, and every call is on record

    Claude Code or any other agent uses the AWS tools at the workspace connection URL, and Traffic shows each call with the request and AWS's answer.

    • The same policies and approvals apply as on any other server
    • Every call is recorded with the agent, the tool and the result
    • Meandr works as the MCP gateway for AWS and for every other server you add
    Connect your first agent, step by step

AWS MCP servers don't take a plain token.

Getting a request in front of an AWS-hosted server takes more than a bearer token — and doing it yourself usually means running something extra.

AWS SigV4, not a bearer token

AWS MCP servers require AWS SigV4-signed requests. A plain API key or bearer token won't get you in — every request needs a valid signature.

Another sidecar to run

The usual workaround is standing up a local proxy just to sign requests — one more process to deploy, patch, and keep alive alongside everything else.

Easy to get wrong by hand

Building the canonical request, wiring up credentials, and getting the region right is fiddly — and a small mistake just fails silently as a rejected request.

How it works

Add the server. Meandr signs. Done.

The signing happens on Meandr's side, on every request — your agents never see it and never need to know it's there. Meandr is an AI agent control plane: your agents connect to one MCP gateway address, and Meandr signs in to every server for them. Each call is checked against your policies, risky ones can wait for a person's approval, and every call is recorded.

01

Add the server

Credentials and region.

Give Meandr the AWS credentials and region for the server, once. Meandr holds them encrypted — your agents never see them.

You set up: AWS credentials and region, in the dashboard.

02

Meandr signs

On every request.

Meandr builds the AWS SigV4 signature for every upstream request to that server, on the fly. Nothing to run yourself, nothing to keep patched.

You set up: nothing more — signing is automatic.

03

Just another server

Governed like the rest.

The AWS MCP server joins your catalog and is governed like any other — the same policies, rate limits, and audit trail apply.

You set up: policies and limits — same as any other server.

Questions you'd ask anyway.

What do I need to connect an AWS MCP server?
AWS credentials with access to the server, and its region. Meandr stores them encrypted and uses them only to sign requests to that server.
Do I need to run a proxy or sidecar myself?
No. Meandr signs each request server-side, on its way to AWS. There's nothing extra for you to deploy or keep running.
Does this actually work today, or is it planned?
It works today. Signing AWS SigV4 requests to real AWS MCP servers is live in Meandr, not a roadmap item.
Can I mix AWS and non-AWS servers?
Yes. Each server keeps its own auth — API keys, custom headers, basic auth, OAuth, mTLS or AWS SigV4 — and they all sit side by side in one catalog.
Which MCP server for AWS can I connect?
Any MCP server on AWS that expects SigV4-signed requests, including the AWS MCP Server itself.

Connect your AWS MCP server without touching a proxy.

Run any MCP server in Meandr or connect the ones you already have, then point every agent at one MCP gateway. Policy, approvals and audit cover every call, with no code changes.

Try for free

Questions? Email us