Strands Agent MCP
The Strands Agent MCP server enables you to:
List all available Strands agents registered with the server
Execute a specific Strands agent by providing its name and a text prompt
Integrates with Amazon Q, allowing for execution of Strands agents through Amazon Q's interface. Users can list available agents and execute them through commands in the Amazon Q chat.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Strands Agent MCPexecute the simple-agent to explain quantum computing basics"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Strands Agent MCP
A Model Context Protocol (MCP) server for executing Strands agents. This project provides a simple way to integrate Strands agents with Amazon Q and other MCP-compatible systems.
IMPORTANT: This project is currently in alpha stage and not yet published on PyPI.
Overview
Strands Agent MCP is a bridge between the Strands agent framework and the Model Context Protocol (MCP). It allows you to:
Register Strands agents as MCP tools
Execute Strands agents through MCP
Find agents by specific skills
The project uses a plugin architecture that makes it easy to add new agents without modifying the core code.
Related MCP server: A2A Client MCP Server
Installation
Note: This package is not yet available on PyPI. You'll need to install it from source.
# Clone the repository
git clone https://github.com/yourusername/strands-agent-mcp.git
cd strands-agent-mcp
# Install the package
pip install -e .Usage
Starting the MCP Server
strands-agent-mcpThis will start the MCP server.
Environment Variables
The server supports the following environment variables:
PLUGIN_PATH: Custom path to look for plugins (default: ".")PLUGIN_NAMESPACE: Custom namespace prefix for plugins (default: 'sap_mcp_plugin')
Creating Agent Plugins
To create a new agent plugin, create a Python package with a name that starts with sap_mcp_plugin_ (sap stands for strands agent plugin). Your package should implement a build_agents function that returns a list of AgentEntry objects:
from typing import List
from boto3 import Session
from strands import Agent
from strands.models import BedrockModel
from strands_agent_mcp.registry import AgentEntry
def build_agents() -> List[AgentEntry]:
return [
AgentEntry(
name="my-agent",
agent=Agent(
model=BedrockModel(boto_session=Session(region_name="us-west-2"))
),
skills=["general-knowledge", "coding"]
)
]Using with Amazon Q
Once the MCP server is running, you can connect it to Amazon Q. Refer to the Amazon Q documentation for the correct connection parameters.
The following MCP tools will be available:
execute_agent: Execute an agent with parametersagent_nameandpromptlist_agents: List all available agents
Architecture
The project consists of three main components:
Server: The MCP server that exposes the agent execution API
Registry: A registry for managing available agents and their skills
Plugins: Dynamically discovered modules that register agents with the registry
The server automatically discovers all installed plugins that follow the naming convention and registers their agents.
Dependencies
fastmcp>=2.3.4: For implementing the MCP serverstrands-agents>=0.1.1: The core Strands agent frameworkstrands-agents-builder>=0.1.0: Tools for building Strands agentsstrands-agents-tools>=0.1.0: Additional tools for Strands agents
Development
This project uses uv for dependency management. To set up a development environment:
Clone the repository
Install uv if you don't have it already:
pip install uvCreate a virtual environment and install dependencies:
uv venv uv sync
Sample Plugin
The repository includes a sample plugin (sap_mcp_plugin_simple) that demonstrates how to create and register a simple agent:
from typing import List
from boto3 import Session
from strands import Agent
from strands.models import BedrockModel
from strands_agent_mcp.registry import AgentEntry
def build_agents() -> List[AgentEntry]:
return [
AgentEntry(
name="simple-agent",
agent=Agent(
model=BedrockModel(boto_session=Session(region_name="us-west-2"))
),
skills=["general-knowledge"]
)
]License
This project is licensed under the terms of the LICENSE file included in the repository.
Available Tools
3 toolsexecute_agentC
Execute an agent with a given prompt
Inputs: agent_name (required), prompt (required).
list_agentsC
list all available agents
Inputs: no named parameters.
list_skillsB
list all available skills for agents
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: execute_agent runs an agent, list_agents enumerates available agents, and list_skills enumerates available skills. The descriptions make it unambiguous which tool to use for each operation.
All three tools follow a consistent verb_noun pattern (execute_agent, list_agents, list_skills) with the same naming convention throughout. The verbs (execute, list) are appropriate and consistently applied.
With only 3 tools, the set feels thin for an agent management system. While the tools cover basic operations (list and execute), there are likely missing capabilities like creating, updating, or deleting agents or skills, which limits the server's scope.
The tool surface is significantly incomplete for agent management. It lacks essential CRUD operations (e.g., create_agent, update_agent, delete_agent, create_skill) and other lifecycle actions (e.g., stop_agent, monitor_agent). This will cause agent failures when trying to perform basic management tasks.
Maintenance
Related MCP Connectors
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
The Remote MCP server acts as a standardized bridge between LLM applications (like Claude, ChatGPT, and Cursor) and external services, enabling AI agents to access external tools and resources. Its primary capability is providing a centralized search tool to discover other MCP servers and their respective tools. Unlike local implementations, it runs remotely with OAuth authentication and permission controls for security.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.410-
- AlicenseAqualityDmaintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.528MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server implementation that can be run directly or through Docker, enabling AI assistants to interact with external systems through the MCP standard.2-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables multiple AI agents to share memory, coordinate tasks, and collaborate effectively across IDEs and CLI tools.42 npm21MIT