Strands Agents MCP Server

Created By
strands-agentsa year ago
This MCP server provides documentation about Strands Agents to your GenAI tools, so you can use your favorite AI coding assistant to vibe-code Strands Agents.
Overview

What is Strands Agents MCP Server?

Strands Agents MCP Server is a model-driven platform that provides documentation about Strands Agents, enabling users to integrate AI coding assistants for efficient coding.

How to use Strands Agents MCP Server?

To use the MCP server, install the required dependencies and configure it with supported applications like Amazon Q Developer CLI, Claude Code, Cline, and Cursor. Follow the installation instructions provided in the documentation.

Key features of Strands Agents MCP Server?

  • Provides comprehensive documentation for Strands Agents.
  • Supports integration with various AI coding assistants.
  • Allows quick testing and troubleshooting using the MCP Inspector.

Use cases of Strands Agents MCP Server?

  1. Integrating AI coding assistants for enhanced coding efficiency.
  2. Testing and troubleshooting MCP server configurations.
  3. Developing AI agents with minimal code.

FAQ from Strands Agents MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server provides documentation and integration capabilities for Strands Agents, facilitating the use of AI coding assistants.

  • Is there a license for the MCP Server?

Yes, the project is licensed under the Apache License 2.0.

  • How can I contribute to the project?

Contributions are welcome! Please refer to the Contributing Guide for details.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
strands-agents
Star
66
Language
Python
License
Apache-2.0 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)

a day ago