When an SMB buyer asks an AI assistant which AWS MCP server to use, a shortlist comes back. We asked 44 different phrasings of that question across 3 engines, 132 answers in total, and counted every product named. This is the result. Nobody paid to be on it, and no vendor list was written in advance — the 58 vendors below are simply everyone the engines named.
Free to read, raw data included. What is for sale — $9.99/mo monitoring for a single vendor.
“Answers” is how many of the 132 answers named that product.
Share is the same number as a percentage. The two right-hand columns split it by engine.
Every row has its own link — the # beside a vendor name gives you
something like connexion.me/c/awsmcp/#aws.
Click a vendor's name to see which of the 44 questions named them, and
click one of those to read the answer it was counted from, word for word.
| # | Vendor | Answers | Share | ChatGPT | Gemini | Perplexity | |
|---|---|---|---|---|---|---|---|
| 1 | AWS MCP Server# | 118 | 89.4% | 35 | 42 | 41 | |
| 2 | AWS API MCP Server# | 33 | 25.0% | 20 | 0 | 13 | |
| 3 | awslabs.ec2-mcp-server# | 12 | 9.1% | 5 | 1 | 6 | |
| 4 | CloudWatch MCP Server# | 5 | 3.8% | 3 | 1 | 1 | |
| 5 | Steampipe MCP Server# | 5 | 3.8% | 0 | 5 | 0 | |
| 6 | @modelcontextprotocol/server-aws# | 4 | 3.0% | 0 | 4 | 0 | |
| 7 | Cloud Control API MCP Server# | 4 | 3.0% | 0 | 0 | 4 | |
| 8 | CloudWatch Logs MCP server# | 4 | 3.0% | 3 | 0 | 1 | |
| 9 | Amazon Bedrock Knowledge Bases Retrieval MCP Server# | 3 | 2.3% | 2 | 0 | 1 | |
| 10 | Amazon ECS MCP Server# | 3 | 2.3% | 0 | 0 | 3 | |
| 11 | Amazon EKS MCP Server# | 3 | 2.3% | 0 | 0 | 3 | |
| 12 | Athena MCP# | 3 | 2.3% | 2 | 1 | 0 | |
| 13 | S3 MCP server# | 3 | 2.3% | 1 | 1 | 1 | |
| 14 | Amazon Bedrock Knowledge Bases MCP Server# | 2 | 1.5% | 1 | 1 | 0 | |
| 15 | awslabs.aws-diagram-mcp-server# | 2 | 1.5% | 2 | 0 | 0 | |
| 16 | Bedrock Knowledge Bases Retrieval MCP# | 2 | 1.5% | 1 | 0 | 1 | |
| 17 | Lambda Tool MCP Server# | 2 | 1.5% | 1 | 0 | 1 | |
| 18 | managed AWS MCP Server# | 2 | 1.5% | 0 | 0 | 2 | |
| 19 | MCP Proxy for AWS# | 2 | 1.5% | 0 | 0 | 2 | |
| 20 | Prowler MCP Server# | 2 | 1.5% | 1 | 1 | 0 | |
| 21 | @mcp-get/aws# | 1 | 0.8% | 0 | 1 | 0 | |
| 22 | alexei-led/aws-mcp-server# | 1 | 0.8% | 0 | 0 | 1 | |
| 23 | Amazon Aurora MySQL MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 24 | Amazon Aurora Postgres MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 25 | Amazon Bedrock Custom Model Import MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 26 | Amazon Bedrock Knowledge Base Retrieval MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 27 | Amazon CloudWatch MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 28 | Amazon DynamoDB MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 29 | Amazon RDS SQL Server MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 30 | Amazon S3 MCP Server# | 1 | 0.8% | 0 | 1 | 0 | |
| 31 | AWS Cloud Control / CCAPI MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 32 | AWS CloudWatch Logs# | 1 | 0.8% | 0 | 0 | 1 | |
| 33 | AWS Cost Explorer / Cost Analysis MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 34 | AWS Documentation / AWS Knowledge MCP server# | 1 | 0.8% | 0 | 0 | 1 | |
| 35 | AWS Knowledge Bases MCP Server# | 1 | 0.8% | 0 | 1 | 0 | |
| 36 | awslabs.aws-api-mcp-server@latest# | 1 | 0.8% | 1 | 0 | 0 | |
| 37 | awslabs.aws-documentation-mcp-server@latest# | 1 | 0.8% | 1 | 0 | 0 | |
| 38 | CloudFormation / AWS CDK MCP Server# | 1 | 0.8% | 0 | 1 | 0 | |
| 39 | CloudFormation MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 40 | Core MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 41 | Cost Analysis MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 42 | DataFaucet EC2 MCP# | 1 | 0.8% | 0 | 0 | 1 | |
| 43 | DynamoDB MCP server# | 1 | 0.8% | 1 | 0 | 0 | |
| 44 | EKS MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 45 | Log Analyzer with MCP# | 1 | 0.8% | 0 | 0 | 1 | |
| 46 | managed remote AWS MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 47 | Model Context Protocol (MCP) Server for AWS# | 1 | 0.8% | 0 | 0 | 1 | |
| 48 | Official AWS Documentation MCP Server# | 1 | 0.8% | 0 | 1 | 0 | |
| 49 | official AWS Labs AWS API MCP Server# | 1 | 0.8% | 1 | 0 | 0 | |
| 50 | official AWS Labs MCP server# | 1 | 0.8% | 1 | 0 | 0 | |
| 51 | official AWS Labs MCP servers# | 1 | 0.8% | 1 | 0 | 0 | |
| 52 | Official AWS MCP Server# | 1 | 0.8% | 0 | 1 | 0 | |
| 53 | OpenSearch MCP server# | 1 | 0.8% | 1 | 0 | 0 | |
| 54 | qodo-ai/aws-mcp# | 1 | 0.8% | 0 | 1 | 0 | |
| 55 | RDS Management MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 56 | S3 Tables MCP Server# | 1 | 0.8% | 0 | 0 | 1 | |
| 57 | stefanpejcic/mcp-server-aws# | 1 | 0.8% | 0 | 1 | 0 | |
| 58 | use_aws_mcp# | 1 | 0.8% | 0 | 0 | 1 |
Everything above is free and stays free — the leaderboard, the method, all 132 raw answers and the machine-readable ranking, published in full at the bottom of this page. No vendor paid to be listed, no vendor can pay to move, and nothing here goes behind a login later.
What is for sale is one vendor's row, watched: $9.99 a month to be told when your rank moves, who took your mentions, and which phrasings started or stopped naming you — the board is re-run monthly and you get what changed. A one-off $199 deep report on a single row is the other option. What is in each →
Every claim on this page is reproducible from the files linked at the bottom.
ChatGPT (gpt-5.5), Gemini (gemini-flash-latest), Perplexity (sonar). Each was called through its public API with a near-empty system prompt —
“answer the user's question directly and concisely” — and nothing else. The engines were
not asked to produce a list, rank anything, or name vendors. Steering them toward a list
would have manufactured the thing being measured.
44 distinct phrasings of one purchase decision, written before any measurement was run. No vendor name appears in any of them.
Each of the 132 answers was read back and every named product extracted. The vendor list is discovered: a product appears here if and only if an engine named it. Counted are Model Context Protocol (MCP) servers, connectors, and plugins designed to connect AI LLMs to AWS infrastructure, Amazon Bedrock, Amazon data stores, or Amazon APIs. Excluded, even when named: generic MCP servers for non-Amazon platforms, standard AWS SDKs and CLI tools lacking MCP support, standalone LLM APIs and foundation model hosting platforms, generic AI agent and orchestration frameworks, workflow automation platforms, vector databases, local AI runtimes, and companies named only as an example cloud hosting destination.
Spelling variants of one product are folded together — “awslabs/mcp-server-aws”, “AWS MCP Server” and “mcp-server-aws” are one row, and a trailing “by company” is dropped. An edition name is folded into its product when the plain name is at least three times as common, so “mcp-server-aws-s3” counts as mcp-server-aws and “AWS Bedrock MCP Server Enterprise” counts as AWS Bedrock MCP Server. No pair was merged by hand in this category: every fold above is the rule applied mechanically, with no human judgement about who is who.
A product is counted once per answer, however many times that answer mentions it.
This check was run before the page was, and it is published at 7/10 rather than smoothed over or withheld. Both runs are linked below in full, so the disagreement is auditable rather than described.
This measures what two answer engines said on 4 Aug 2026, in response to these questions, through their APIs. It is not a quality ranking, not a review, and not advice on which AWS MCP server to use. A product can be excellent and rank low here — that gap is the point.
All 132 answers, verbatim, one JSON object per line: run A · run B. The per-answer extracted product names: run A · run B. Machine-readable ranking: ranking.json.
The answer a vendor panel shows you is read straight out of the run A file linked above — the page fetches the one line it needs and displays it unaltered, so what you read there and what you get by downloading the file are the same bytes.