Strands Agent MCP
股线代理 MCP
用于执行 Strands 代理的模型上下文协议 (MCP) 服务器。该项目提供了一种将 Strands 代理与 Amazon Q 及其他兼容 MCP 的系统集成的简单方法。
概述
Strands Agent MCP 是 Strands 代理框架和模型上下文协议 (MCP) 之间的桥梁。它允许您:
将 Strands 代理注册为 MCP 工具
通过 MCP 执行 Strands 代理
发现并列出可用的代理
该项目采用插件架构,可以轻松添加新代理,而无需修改核心代码。
Related MCP server: A2A Client MCP Server
安装
pip install strands-agent-mcp用法
启动 MCP 服务器
strands-agent-mcp这将在默认端口上启动 MCP 服务器。
创建代理插件
要创建新的代理插件,请创建一个以sap_mcp_plugin_开头的 Python 包(sap 代表 strands agent plugin)。您的包应该实现一个register_plugin函数,该函数用于向提供的注册表注册一个或多个代理:
from strands import Agent
from strands.models import BedrockModel
from strands_agent_mcp.registry import Registry
def register_plugin(registry: Registry) -> None:
registry.register("my-agent", Agent(
model=BedrockModel(boto_session=Session(region_name="us-west-2")))
)与 Amazon Q 一起使用
一旦 MCP 服务器运行,您就可以将代理与 Amazon Q 一起使用:
q chat --mcp-server http://localhost:8000然后您可以在聊天中使用以下命令:
列出可用的代理:
strands___list_agentslist_agents执行代理:
strands___execute_agentexecute_agent,参数为agent(代理名称)和prompt(发送给代理的提示)
建筑学
该项目由三个主要部分组成:
服务器:暴露代理执行 API 的 MCP 服务器
注册表:用于管理可用代理的简单注册表
插件:动态发现向注册表注册代理的模块
服务器自动发现所有遵循命名约定的已安装插件并注册其代理。
依赖项
fastmcp:用于实现 MCP 服务器strands-agents:核心 Strands 代理框架strands-agents-builder:用于构建 Strands 代理的工具strands-agents-tools:Strands 代理的附加工具
发展
要设置开发环境:
克隆存储库
创建虚拟环境:
python -m venv .venv激活虚拟环境:
source .venv/bin/activate(Linux/Mac)或.venv\Scripts\activate(Windows)安装开发依赖项:
pip install -e ".[dev]"
创建测试插件
该存储库包含一个示例插件( sap_mcp_plugin_test ),它演示了如何创建和注册一个名为“simple-agent”的简单代理:
from boto3 import Session
from strands import Agent
from strands.models import BedrockModel
from strands_agent_mcp.registry import Registry
def register_plugin(registry: Registry) -> None:
registry.register("simple-agent", Agent(
model=BedrockModel(boto_session=Session(region_name="us-west-2")))
)执照
[在此处添加许可信息]
Available Tools
3 toolsexecute_agentC
Execute an agent with a given prompt
| Name | Required | Description | Default |
|---|---|---|---|
| agent_name | Yes | The name of the agent to execute | |
| prompt | Yes | The prompt to execute the agent with |
list_agentsC
list all available agents
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_skillsB
list all available skills for agents
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
v1.0.0- First observed
execute_agent - First observed
list_agents - First observed
list_skills
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