Back to catalog
A

Official Vendor Server

Amazon Web Services✦ Lab Verified

AWS Documentation

Access and search AWS documentation. Read docs pages, extract sections, and get content recommendations.

9.4/10

Score

445ms

Latency

Local

Uptime

4

Tools

stdio

Auth

Officialvendor-verifiedsecurity-scanneddocumentation

Ecosystem

Amazon Web Services MCP Servers

8 specialized servers, 106 tools tested independently. Each link leads to a full review with tool-level evidence.

ServerScoreSecurity
AWS IAM94/1009/10
AWS93/1009/10
AWS Cost Explorer92/1009/10
AWS Well-Architected Security92/1009/10
AWS Billing91/1008/10
AWS Pricing91/1008/10
AWS CloudTrail90/1008/10
AWS CloudWatch90/1008/10
4 discovered4 executed4 success
Median latency: 445ms

Quick Verdict

Use this for AWS documentation lookups and service research. Avoid it if you need live AWS resource data. Best area: documentation reads with 445ms median response. Biggest failure: none in current tests.

Lab Review

What We Found

What works: The core documentation retrieval tools performed consistently across all test cases. read_documentation and read_sections delivered complete AWS service guides and targeted content without errors. Response times varied appropriately by operation complexity, from 134ms for sections to 1960ms for complete service guides that can be cached for subsequent fast access. Where it breaks: We encountered no tool failures during testing. All 4 operations completed successfully with proper JSON responses. search_documentation takes 1960ms to search across AWS documentation, which is reasonable for the scope of content being searched. The server maintained reliability across different query types and content sizes. What this means for your workflow: You can build documentation workflows on this server with confidence. Section reads and searches performed reliably in current tests, giving you consistent access to AWS documentation without worrying about rate limits or authentication complexity. The varied response times match operation complexity naturally. For any team building AWS documentation tools or AI assistants that need reliable AWS reference data, this server delivers. For teams needing sub-second responses across all operations, factor in the search latency.

Lab Observations

What actually happened during testing

During testing, our scanner interacted with AWS Documentation. 4 tools succeeded.

ToolStatus
read_documentation success
read_sections success
search_documentation success
recommend success

Reliability

10/10

Full runtime test completed. Score based on transport stability and schema completeness.

Score Breakdown

10/10

Reliability

4 of 4 executed tools succeeded.

9/10

Security

Score based on schema analysis and dependency audit.

9/10

Setup

Local stdio server. Install via npx or binary, no auth required.

8.9/10

Docs

4 tools with descriptions and input schemas.

10/10

Compatibility

Standard MCP protocol. Transport: stdio.

9.4/10

Maintenance

Based on commit frequency, releases, and contributor activity.

Tools

4 available tools

read_documentation

Fetch and convert an AWS documentation page to markdown format. ## Usage This tool retrieves the content of an AWS documentation page and converts it to markdown format. For long documents, you can make multiple calls with different start_index values to retrieve the entire content in chunks. ## URL Requirements - Must be from the docs.aws.amazon.com domain - Must end with .html ## Example URLs - https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html - https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html ## Output Format The output is formatted as markdown text with: - Preserved headings and structure - Code blocks for examples - Lists and tables converted to markdown format ## Handling Long Documents If the response indicates the document was truncated, you have several options: 1. **Continue Reading**: Make another call with start_index set to the end of the previous response 2. **Stop Early**: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read max_length: Maximum number of characters to return start_index: On return output starting at this character index Returns: Markdown content of the AWS documentation

read_sections

Extract specific sections from AWS documentation pages by title. Retrieves a page, converts to markdown, and returns only matching sections. Section matching is case-insensitive and handles whitespace differences. ## URL Requirements - Must end with .html ## Read Sections Tips - Use exact section titles from search results 'sections' field when available - Section matching is case-insensitive and handles whitespace differences - Include multiple related sections in one call for comprehensive coverage ## Example Usage ``` # If query is about S3 bucket naming rules: # Available sections: ['General purpose buckets naming rules', 'Example general purpose bucket names', 'Best practices', 'Creating a bucket that uses a GUID in the bucket name'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/s3/latest/userguide/bucketnamingrules.html', section_titles=['General purpose buckets naming rules', 'Best practices'], ) # If query is about Python Lambda function examples: # Available sections: ['Example Python Lambda function code', 'Handler naming conventions', 'Using the Lambda event object', 'Accessing and using the Lambda context object'. 'Valid handler signatures for Python handlers', 'Returning a value', 'Using the AWS SDK for Python (Boto3) in your handler', 'Accessing environment variables, 'Code best practices for Python Lambda functions'] # Read these specific sections: read_sections( url='https://docs.aws.amazon.com/lambda/latest/dg/python-handler.html', section_titles=[ 'Example Python Lambda function code', 'Code best practices for Python Lambda functions', ], ) ``` Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to read section_titles: List of section titles to extract Returns: Filtered markdown content containing only the requested sections

search_documentation

Search AWS documentation using the official AWS Documentation Search API. ## Usage This tool searches across all AWS documentation for pages matching your search phrase. Use it to find relevant documentation when you don't have a specific URL. ## Search Tips - Use specific technical terms rather than general phrases - Include service names to narrow results (e.g., "S3 bucket versioning" instead of just "versioning") - Use quotes for exact phrase matching (e.g., "AWS Lambda function URLs") - Include abbreviations and alternative terms to improve results - Use guide_type and product_type filters found from a SearchResponse's "facets" property: - Filter only for broad search queries with patterns: - "What is [service]?" -> product_types: ["Amazon Simple Storage Service"] - "How to use <service 1> with <service 2>?" -> product_types: [<service 1>, <service 2>] - "[service] getting started" -> product_types: [<service>] + guide_types: ["User Guide, "Developer Guide"] - "API reference for [service]" -> product_types: [<service>] + guide_types: ["API Reference"] ## Result Interpretation Each SearchResponse includes: - search_results: List of documentation pages, each with: - rank_order: The relevance ranking (lower is more relevant) - url: The documentation page URL - title: The page title - context: A brief excerpt or summary (if available) - sections: Table of contents (when available) - these section titles can be used with the read_sections tool for targeted content extraction - facets: Available filters (product_types, guide_types) for refining searches - query_id: Unique identifier for this search session Args: ctx: MCP context for logging and error handling search_phrase: Search phrase to use search_intent: The intent behind the search requested by the user limit: Maximum number of results to return product_types: Filter by AWS product/service guide_types: Filter by guide type Returns: List of search results with URLs, titles, query ID, context snippets, and facets for filtering

recommend

Get content recommendations for an AWS documentation page. ## Usage This tool provides recommendations for related AWS documentation pages based on a given URL. Use it to discover additional relevant content that might not appear in search results. ## Recommendation Types The recommendations include four categories: 1. **Highly Rated**: Popular pages within the same AWS service 2. **New**: Recently added pages within the same AWS service - useful for finding newly released features 3. **Similar**: Pages covering similar topics to the current page 4. **Journey**: Pages commonly viewed next by other users ## When to Use - After reading a documentation page to find related content - When exploring a new AWS service to discover important pages - To find alternative explanations of complex concepts - To discover the most popular pages for a service - To find newly released information by using a service's welcome page URL and checking the **New** recommendations ## Finding New Features To find newly released information about a service: 1. Find any page belong to that service, typically you can try the welcome page 2. Call this tool with that URL 3. Look specifically at the **New** recommendation type in the results ## Result Interpretation Each recommendation includes: - url: The documentation page URL - title: The page title - context: A brief description (if available) Args: ctx: MCP context for logging and error handling url: URL of the AWS documentation page to get recommendations for Returns: List of recommended pages with URLs, titles, and context

FAQ

Frequently asked questions about AWS Documentation

What latency should I expect for different AWS documentation operations?+

Response times scale appropriately with operation complexity. Section reads complete in 134ms, targeted documentation retrieval takes 445ms, and recommendations finish in 201ms. Comprehensive search operations across the full AWS documentation require 1960ms but deliver thorough results that can be cached for subsequent fast lookups.

Does the search functionality return accurate AWS documentation results?+

Our testing confirmed that search_documentation successfully retrieved relevant AWS service information when queried. The search operation processes queries against the comprehensive AWS documentation set, returning structured results that matched our test queries for specific AWS services and features.

Can I retrieve specific sections of AWS documentation without downloading entire guides?+

The read_sections tool allows targeted retrieval of specific documentation sections, completing in 134ms during our tests. This provides faster access than full document retrieval when you need specific information rather than comprehensive service guides.

What authentication is required to access AWS documentation through this server?+

Our tests used none credentials with docs:read scope to access all documentation features. The server connected successfully through local_stdio transport without requiring AWS account credentials, since it accesses public AWS documentation rather than account-specific resources.

Does the recommendation system provide useful AWS service suggestions?+

The recommend tool successfully generated AWS service recommendations during our testing, completing responses in 201ms. The tool processed our input requirements and returned structured recommendations for relevant AWS services based on the query parameters we provided.

Are there any AWS documentation features that aren't accessible through this server?+

Our testing covered the four core documentation tools without encountering any excluded functionality. However, testing was limited to basic documentation access patterns. Advanced features like personalized documentation or account-specific guidance may exist outside our test scope.

Related

Explore more

Testing History

1 runlive_runtimeApr 7, 2026
protocol10/10reliability10/10

Community

Community Reviews