Ext Ops Panel
Open dashboard
Comparison

AWS CDK vs Arkansas Code

AWS CDK is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Arkansas Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAWS CDKArkansas Code
Docker MCP Catalog Listed
Version: sha256:6973319affc4
Forks (GitHub): 1 820
Pulls (Docker Hub): 49 560
Stars (Docker Hub): 0
Stars (GitHub): 9 803
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

AWS CDK vs Arkansas Code
FactAWS CDKArkansas Code
Marketplaces that list it11
Stars (GitHub) (differs)9 803 (better)0 (worse)
Pulls (Docker Hub) (differs)49 560No figure on Docker Hub
Forks (GitHub) (differs)1 820 (better)0 (worse)
Last release (differs)Not published2026-10-19
Where it runs (differs)On your machine (mcp/aws-cdk-mcp-server)Remote server (gateway.pipeworx.io/arkansas-code/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpgithub.com/pipeworx-io/mcp-arkansas-code
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 35 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

AWS CDK

In its own words, on Docker MCP Catalog:

AWS Cloud Development Kit (CDK) best practices, infrastructure as code patterns, and security compliance with CDK Nag.

Arkansas Code

In its own words, on Official MCP Registry:

Arkansas Code of 1987 — state statutes by citation and by topic search. Fleet #2881, closing the…

How to run each

AWS CDK As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-cdk-mcp-server -- docker run -i --rm mcp/aws-cdk-mcp-server

Arkansas Code As a remote MCP server

Claude Code
claude mcp add --transport http arkansas-code https://gateway.pipeworx.io/arkansas-code/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Arkansas Code has a remote endpoint we check. How we check endpoints

Tools each declares

Only AWS CDK has

  • CDKGeneralGuidance
  • CheckCDKNagSuppressions
  • ExplainCDKNagRule
  • GenerateBedrockAgentSchema
  • GetAwsSolutionsConstructPattern
  • LambdaLayerDocumentationProvider
  • SearchGenAICDKConstructs

Only Arkansas Code has

  • ai_visibility_check
  • ar_search
  • ar_statute
  • archive_compare
  • archive_evidence
  • ask_pipeworx
  • ask_pipeworx_beta
  • ask_pipeworx_grounded
  • bet_research
  • classify_row
  • company_facts
  • company_register_search
Show the remaining 31
  • compare_entities
  • deep_research
  • discover_tools
  • entity_profile
  • forget
  • generate_llms_txt
  • kalshi_weather_edge
  • list_subscriptions
  • pipeworx_feedback
  • pipeworx_trending
  • polymarket_arbitrage
  • polymarket_edge_tracker
  • polymarket_edges
  • polymarket_fill_risk
  • polymarket_kalshi_spread
  • recall
  • recent_alerts
  • recent_changes
  • release_calendar_markets
  • remember
  • research_row
  • resolution_audit
  • resolution_diff
  • resolve_entity
  • scan_competitor_ai_presence
  • scan_dependency
  • search_within
  • subscribe
  • suggest_questions
  • unsubscribe
  • validate_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Arkansas Code as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AWS CDK · What it can do: Arkansas Code · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built