Query multiple AWS accounts across orgs at once from your AI chat client, via IAM Identity Center SSO. Rule-based role selection, no long-lived keys.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aws-sso-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# aws-sso-mcp **Got more than one AWS account or org? Sign in once, ask in plain English, and get one merged answer from all of them, using the IAM roles your rules choose, never the AI's.** `aws-sso-mcp` is an [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server. It plugs into a chat assistant such as GitHub Copilot Chat in VS Code or Claude Desktop, and lets that assistant query and manage AWS through your **AWS IAM Identity Center (SSO)** login. > *"List all stopped EC2 instances across every prod account in org1."* > > One sentence in. One combined answer out, from every matching account. ## Contents - [Is this for you?](#is-this-for-you) - [Why this exists](#why-this-exists) - [What you can do with it](#what-you-can-do-with-it) - [How it works in 30 seconds](#how-it-works-in-30-seconds) - [Quick start](#quick-start) - [Safety model](#safety-model) - [Documentation map](#documentation-map) - [Project layout](#project-layout) - [Requirements and status](#requirements-and-status) - [Security](#security) - [Contributing](#contributing) - [License](#license) ## Is this for you? **If you work in more than one AWS account, yes.** The more accounts and orgs you have, the more it saves you. - **Several orgs.** Keep every org in one config file. Switch between them in chat, or query several in a single request. Each org needs its own login, and you never mix them up by accident. - **Dozens or hundreds of accounts.** Find accounts by name, id or environment, then ask one question of all of them. No account-by-account console hopping, no profile juggling. - **A different role per account.** Prod gets `ReadOnlyAccess`, sandboxes get `PowerUserAccess`. You write that once, and it is applied everywhere. - **Questions that cross accounts.** "Where is this running?", "Which accounts have public buckets?", "What is stopped in prod?" Each is one sentence instead of an afternoon of clicking. If you only ever use a single account, it still works,…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.