AgentSidekick

Better agent tooling for AWS

Integration gap · Measured demandOverall 53.9 / 100 DERConfidence Medium DERCalculated

6,561 public GitHub issues mention "AWS mcp" (checked 2026-11-21) SRC, while 162 indexed products mention AWS DER. On the six weighted components it scores 53.9 of 100, confidence Medium, as of 2026-11-21.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2592.00.25 × 92.0 = 23.00Measured
Competition gap0.200.00.20 × 0.0 = 0.00Measured
Monetisation0.2065.00.20 × 65.0 = 13.00Heuristic
Growth (relative)0.1513.00.15 × 13.0 = 1.95Measured
Feasibility0.1080.00.10 × 80.0 = 8.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0053.85 → 53.9

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Medium

Rule: Medium when at least 50 GitHub issues mention the integration and at least 10 indexed products mention it; otherwise Low. Nothing is rated High.

What would raise it

  • Medium is the highest level the rules assign. High would need a second, independent demand source (search volume or marketplace installs), which is not connected.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Developers are asking for AWS access from AI agents more than the current supply of well-maintained tools would suggest.DER
Problem
Agents need to read from and act on AWS. Only some of the existing tools are both documented and actively maintained.DER
Target users
Teams that already pay for AWS and want agents to work inside itHEU
Product form
MCP server (optionally bundled as a plugin with skills)HEU
Revenue model
Hosted/remote server with per-seat or usage pricingHEU
Complexity
Low to mediumHEU
Competition level
HighDER
Subject
AWS (integration)

Evidence for

4 row(s) from opportunity_evidence.

  • DemandMeasuredDERvalue 6,561

    6561 public GitHub issues contain the phrase "AWS mcp" (checked 2026-11-21); that is the 92th percentile of the 108 integrations tracked. Issue mentions measure developer discussion, not buyers.

    Source

  • MonetisationHeuristicHEU

    AWS is sold mainly to businesses on paid plans, which suggests buyers with budget. This is a rule of thumb, not revenue data.

  • FeasibilityHeuristicHEU

    AWS has a public API (documentation linked).

    Source

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support, so one MCP server can reach all of them.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • Competition gapMeasuredDERvalue 110

    162 indexed products mention AWS; 110 of them have a complete record and a repository pushed in the last 180 days.

    /integrations/aws/

  • Growth (relative)MeasuredDERvalue 43

    43 products launched in the last 90 days versus 35 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.

  • Competition gapMeasuredDERvalue 7

    7 indexed product(s) are published under a namespace matching AWS itself (AWS MCP Server, AWS MCP Server, aws-agents). The gap score was reduced by 25 points for that.

    /integrations/aws/

Existing products

All AWS products

The most notable profiled products mentioning AWS (up to 8). 162 indexed in total.

mcp

MCP serverby awslabsHEU

9.9k GitHub starspushed todayApache-2.0

LLM-Engineers-Handbook

Infrastructureby PacktPublishingHEU

5.4k GitHub starspushed 7mo agoMIT

aws-agents

Pluginby awsSRC

3.5k GitHub starspushed todayApache-2.0

aws-core

Pluginby awsSRC

3.5k GitHub starspushed todayApache-2.0

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
162DER
With a full profile
8+DER
Launches, last 90 days
43 vs 35 in the 90 beforeSRC
Demand measured
SRC
Segment calculated
Score calculated

Risks and counterarguments

  • The vendor may ship (or already ships) an official AWS server, which usually becomes the default.
  • Issue mentions measure developer discussion, not willingness to pay.
  • 162 indexed products mention AWS; 110 of them have a complete record and a repository pushed in the last 180 days.
  • 43 products launched in the last 90 days versus 35 in the previous 90; the whole catalogue went from 14427 to 45454, and the score is relative to that.
  • 7 indexed product(s) are published under a namespace matching AWS itself (AWS MCP Server, AWS MCP Server, aws-agents). The gap score was reduced by 25 points for that.
  • The catalogue already holds at least 5 products for AWS published by an account named after it: aws-agents (aws), aws-agents-for-devsecops (aws), aws-core (aws), aws-data-analytics (aws), aws-startup-advisor (aws). That may be the vendor's own server; an account name is not proof.

Assumptions

What has to be true for the score to mean anything.

  • Mentions of "AWS mcp" in GitHub issues reflect developers wanting AWS access from agents.
  • Products that mention the integration in their description or package metadata are the competing supply; ones that do not name it are missed.
  • "Well-maintained" means data completeness ≥ 0.6 and a repository push in the last 180 days.
  • Percentiles compare this integration only with the other integrations tracked, not with the wider market.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. Run the demand query on GitHub: https://github.com/search?q=%22AWS%20mcp%22%20in%3Atitle%2Cbody%20is%3Aissue&type=issues. Compare the count with 6,561 on 2026-11-21; read a sample of issues to see whether they ask for agent access or merely mention it.
  2. Check the supply on the AWS page and search the official MCP Registry and the vendor's own app directory for an official server.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .