Skip to content

Conversation

@arangatang
Copy link
Contributor

@arangatang arangatang commented Feb 2, 2026

Fixes #

Summary

Changes

Established consistent three-tier terminology system across all repository documentation to clearly distinguish between:

  1. "MCP Servers for AWS" - Umbrella term for the entire ecosystem (AWS MCP product + domain-specific servers)
  2. "domain-specific MCP servers for AWS" - This repository's open-source collection
  3. "AWS MCP" or "official AWS MCP server" - The managed AWS product

Files updated:

  • README.md - Updated title, section headings, and TOC; simplified phrases like "installed MCP servers"; changed stdio statement to "The MCP servers in this repository are designed to support stdio only";
    fixed broken TOC anchor link
  • samples/README.md - Updated title and references
  • wasabi-toolbag/content/workspace-summary.md - Updated project title and description
  • src/aws-dataprocessing-mcp-server/README.md - Updated repository reference
  • src/eks-mcp-server/README.md - Updated repository reference
  • docusaurus/docs/samples/index.md - Updated title
  • docusaurus/docs/installation.md - Simplified phrasing, removed redundant qualifiers
  • All other documentation files reviewed and verified for consistency
  • Invalid name used for MCP Proxy for AWS was also fixed

User experience

Before:

  • Inconsistent terminology throughout documentation created ambiguity about whether users were working with the managed AWS MCP product or the open-source domain-specific servers in this repository
  • Mixed usage of "AWS MCP Servers," "MCP Servers for AWS," and other variations
  • Verbose phrases like "installed MCP servers for AWS" where context made qualification unnecessary

After:

  • Clear, consistent terminology that distinguishes between the umbrella ecosystem, this repository's collection, and the managed AWS product
  • Users can immediately understand whether content refers to the entire MCP Servers for AWS ecosystem or specifically to the domain-specific servers in this repository
  • Cleaner, more concise phrasing throughout (e.g., "installed MCP servers")
Screen.Recording.2026-02-02.at.19.09.56.mov

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • I have reviewed the contributing guidelines
  • I have performed a self-review of this change
  • Changes have been tested (npm ci && npm run build && npm run serve)
  • Changes are documented (documentation-only change)

Is this a breaking change? (Y/N) N

RFC issue number: N/A (documentation clarification)

Checklist:

  • Migration process documented
  • Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.

@codecov
Copy link

codecov bot commented Feb 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.85%. Comparing base (9990394) to head (bc09c16).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2353      +/-   ##
==========================================
- Coverage   90.86%   90.85%   -0.01%     
==========================================
  Files         968      968              
  Lines       69885    69885              
  Branches    11389    11389              
==========================================
- Hits        63499    63497       -2     
  Misses       3922     3922              
- Partials     2464     2466       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@arangatang
Copy link
Contributor Author

V2 -

  1. Made it into Open Source MCP Servers for AWS for repository specific text, kept MCP Servers for AWS when applicable to any MCP server offered by AWS.
  2. Added a Essential: and Core: segment of the category descriptions (previously these were undocumented but selectable)
  3. Added (in preview) to the AWS MCPUpdated some cards to remove the AWS MCP annotation
Screen.Recording.2026-02-03.at.11.23.41.mov

Copy link
Contributor

@justintlewis justintlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor comments. Overall I am good with this naming approach.

@arangatang
Copy link
Contributor Author

Note, I ran npm ci && npm run build && npm run serve to verify build compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To triage

Development

Successfully merging this pull request may close these issues.

3 participants