AWS Amplify Gen 2 Documentation MCP Server

Created By
unirta year ago
This MCP server provides tools to access AWS Amplify Gen 2 documentation and search for content. (not official)
Overview

What is AWS Amplify Gen 2 Documentation MCP Server?

This MCP server provides tools to access AWS Amplify Gen 2 documentation and search for content, serving as an unofficial resource for developers.

How to use AWS Amplify Gen 2 Documentation MCP Server?

To use this MCP server, install the required dependencies and configure it in your Amazon Q or Claude environment by adding the provided configuration to your MCP config file.

Key features of AWS Amplify Gen 2 Documentation MCP Server?

  • Read Documentation: Fetch and convert AWS Amplify Gen 2 documentation pages to markdown format.
  • Search Documentation: Search AWS Amplify Gen 2 documentation using the official AWS Amplify Gen 2 Documentation Search API.

Use cases of AWS Amplify Gen 2 Documentation MCP Server?

  1. Fetching detailed explanations from AWS Amplify documentation.
  2. Searching for specific topics or configurations in AWS Amplify Gen 2 documentation.

FAQ from AWS Amplify Gen 2 Documentation MCP Server?

  • Is this MCP server official?

No, this is an unofficial MCP server inspired by the AWS Documentation MCP Server.

  • What are the installation requirements?

You need to install uv from Astral and Python 3.13 or newer.

  • How can I search for documentation?

Use the search_amplify_documentation tool with your search phrase to find relevant documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
unirt
Star
0
Language
HTML
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago