Skip to main content
Glama
hey-iam-ryan

aws-knowledge-plus

by hey-iam-ryan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_KNOWLEDGE_PLUS_TIMEOUTNoPer-request timeout, seconds.20
AWS_KNOWLEDGE_PLUS_CACHE_TTLNoResponse cache TTL, seconds.900
AWS_KNOWLEDGE_PLUS_USER_AGENTNoOverride the default Chrome-like user agent (with care).
AWS_KNOWLEDGE_PLUS_ENABLE_BUILDERNoSet 0 to drop Builder Center from federated search.1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_aws_knowledgeA

Search AWS knowledge sources that the official AWS Knowledge MCP Server does not cover.

Use this for: troubleshooting threads where someone hit the same error ('repost'), anything about Kiro itself such as steering, hooks, specs, powers or MCP configuration ('kiro'), and the AWS Builders' Library or other community write-ups ('builder').

The Builders' Library is worth calling out: aws.amazon.com/builders-library/ redirects to Builder Center, and the official server refuses the redirect target, so this is the only way to find those articles here. Note that Builder Center results carry no article body — see read_aws_content.

Do NOT use this for AWS service documentation, API references, AWS blogs, What's New announcements, Well-Architected guidance or re:Post Knowledge Center articles — the official AWS Knowledge MCP Server indexes those and is the better answer for them.

Sources are queried in parallel; one slow or broken source degrades to an entry in errors rather than failing the call. Snippets are kept short on purpose: pick the promising hits and pass their URLs to read_aws_content.

read_aws_contentA

Fetch a page from a supported source and return it as markdown.

Dispatches on the URL's host:

  • repost.aws/questions/<id> — the question plus every answer, rebuilt from the page's schema.org QAPage data with authors, dates and vote counts.

  • kiro.dev/docs/... — the published markdown twin of the page, so the text arrives without site chrome. Blog and changelog pages are converted from HTML.

  • builder.aws.com/content/... — title, plus a summary when the site's feed published one. The body is client-rendered and is not retrieved, and the response says so; hand the user the URL rather than paraphrasing what came back. A title derived from the URL slug is flagged in meta.title_source.

Long pages are truncated with an explicit marker telling you the start_index to resume from.

list_sourcesA

List the sources this server covers, their limits, and what it deliberately omits.

Call this when unsure whether a lookup belongs here or with the official AWS Knowledge MCP Server.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: search for finding content, list_sources for orienting on scope, and read_aws_content for retrieving a specific page. The descriptions explicitly cross-reference each other to prevent confusion.

Naming Consistency5/5

All three tool names follow a consistent verb_noun snake_case pattern: search_aws_knowledge, list_sources, read_aws_content. The naming style is uniform and predictable.

Tool Count5/5

Three tools is well-scoped for a focused supplementary server that deliberately covers only what the official AWS Knowledge MCP Server misses. Each tool fills an essential role in the search-and-read workflow without bloat.

Completeness5/5

The server covers the full intended lifecycle: discover what sources exist (list_sources), search them (search_aws_knowledge), and retrieve specific content (read_aws_content). This is a complete minimal surface for a supplemental knowledge server.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources