Aws Service Authorization Reference MCP Server

Aws Service Authorization Reference MCP server exists for a simple reason — assistants are far more useful when they can act on Aws Service Authorization Reference directly instead of describing what you should do. # AWS Service Reference Information MCP Server A Model Context Protocol server providing access to AWS Service Reference Information. This server enables LLMs to retrieve IAM actions, resources and conditions keys. # Blog posts! Here is a.

What you get

AWS Service Authorization Reference is a piece of documentation available here where AWS gives exhaustive reference data on all IAM Actions, Resources and Condition Keys, grouping information that was otherwise scattered across multiple service documentations.

Setting it up

@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

What the assistant can call

Once Aws Service Authorization Reference is connected, these are the calls the assistant has available:

• service_codes — Lists all service codes for which we have documentation available
• service_stats — Tells how many Actions, Resources and Condition Keys are documented
• service_actions — A comma-separeted list of all actions for a service
• service_resources — A comma-separeted list of all resources for a service
• service_condition_keys — A comma-separeted list of all conditions keys for a service
• service_action_information — Retrieve the authorization reference data (resources and condition keys) for a single AWS service action
• service_resource_information — Retrieve the authorization reference data (resources and condition keys) for a single AWS service action
• service_condition_key_information — Retrieve the authorization reference data (resources and condition keys) for a single AWS service action

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aws service authorization reference mcp server does with a few real requests.

Choosing this one

Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Aws Service Authorization Reference's toolset — service_codes, service_stats, service_actions and 5 more — is a fair guide to whether it matches your workflow. It is maintained by psantus; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.