MCP client tool for exoclaw — connects to MCP servers and wraps their tools
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":"exoclaw-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.
# exoclaw-tools-mcp MCP client for exoclaw — connects to MCP servers over stdio, SSE, or streamable HTTP and registers their tools as native exoclaw tools. ## Install ``` pip install exoclaw-tools-mcp ``` ## Usage ```python from contextlib import AsyncExitStack from exoclaw.agent.tools.registry import ToolRegistry from exoclaw_tools_mcp.tool import connect_mcp_servers from exoclaw_tools_mcp.config import MCPServerConfig stack = AsyncExitStack() registry = ToolRegistry() await connect_mcp_servers( mcp_servers={ "filesystem": MCPServerConfig(command="npx", args=["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]), "my-api": MCPServerConfig(url="https://example.com/mcp"), }, registry=registry, stack=stack, ) # registry now contains all tools from both servers as mcp_<server>_<tool> entries ``` Transport type is inferred automatically: `command` → stdio; URLs ending in `/sse` → SSE; other URLs → streamable HTTP. Custom headers and per-tool timeouts are supported via `MCPServerConfig`.
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.