Expose Strands Agents tools as an MCP server via stdio transport
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"strands-tools-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# strands-tools-mcp Expose [Strands Agents](https://github.com/strands-agents/sdk-python) tools as an MCP server via stdio transport, so any MCP client (Kiro, Claude Desktop, etc.) can use them. Supports both `@tool`-decorated functions and `TOOL_SPEC` module-based tools from the `strands-agents-tools` package, as well as custom tool files. ## Installation ```bash pip install strands-tools-mcp ``` Or from source: ```bash git clone https://github.com/mkmeral/strands-tools-mcp.git cd strands-tools-mcp pip install -e ".[dev]" ``` ## Configuration Configure which tools to expose via environment variables: | Variable | Description | Example | |---|---|---| | `STRANDS_TOOLS` | Comma-separated tool names from the `strands-agents-tools` package | `shell,http_request,current_time,file_read` | | `STRANDS_TOOLS_PATHS` | Comma-separated file paths **or URLs** to custom `.py` tool files | `/path/to/my_tool.py,https://raw.githubusercontent.com/user/repo/main/tool.py` | Both variables can be used together. At least one must be set. ## Usage ### As a CLI ```bash STRANDS_TOOLS=current_time,shell strands-tools-mcp ``` ### In Kiro / Claude Desktop MCP Config Add to your MCP configuration file: ```json { "mcpServers": { "strands-tools": { "command": "strands-tools-mcp", "env": { "STRANDS_TOOLS": "shell,http_request,file_read,file_write" } } } } ``` ### With Custom Tools You can combine built-in Strands tools with your own custom tool files: ```json { "mcpServers": { "my-tools": { "command": "strands-tools-mcp", "env": { "STRANDS_TOOLS": "current_time", "STRANDS_TOOLS_PATHS": "/path/to/my_tool.py" } } } } ``` ### With Remote Tools (URLs) Point directly at raw GitHub links, gists, or any hosted `.py` file: ```json { "mcpServers": { "remote-tools": { "command": "strands-tools-mcp", "env": { "STRANDS_TOOLS_PATHS": "https://raw.githubusercontent.com/user/repo/…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.