I’ve been working on Polymcp, an open-source toolkit for building MCP agents that can discover, inspect, and orchestrate tools across multiple MCP servers (HTTP, stdio, or in-process).
A few things that might be interesting to this crowd:
• Tool Inspector: a built-in inspector that lets you see exactly which tools are exposed by each MCP server, their schemas, inputs/outputs, and how the agent is reasoning about using them. It’s meant to make MCP setups debuggable instead of opaque.
• Unified agent: one agent can talk to multiple MCP servers at once (local Python tools, remote HTTP servers, stdio MCPs like Playwright, etc.).
• Code-mode execution: instead of iterative “LLM → tool → LLM → tool” loops, the agent can generate a single Python script that executes the full tool plan. This is faster, cheaper in tokens, and easier to audit.
• Minimal boilerplate for servers: you can expose plain Python functions as MCP tools with almost no glue code.
• CLI + registry: manage MCP servers, configs, and agents from the CLI; servers can be added/removed without touching agent code.
The goal is to make MCP setups feel more like a composable systems tool than a black-box agent framework.
I’ve been working on Polymcp, an open-source toolkit for building MCP agents that can discover, inspect, and orchestrate tools across multiple MCP servers (HTTP, stdio, or in-process).
A few things that might be interesting to this crowd: • Tool Inspector: a built-in inspector that lets you see exactly which tools are exposed by each MCP server, their schemas, inputs/outputs, and how the agent is reasoning about using them. It’s meant to make MCP setups debuggable instead of opaque. • Unified agent: one agent can talk to multiple MCP servers at once (local Python tools, remote HTTP servers, stdio MCPs like Playwright, etc.). • Code-mode execution: instead of iterative “LLM → tool → LLM → tool” loops, the agent can generate a single Python script that executes the full tool plan. This is faster, cheaper in tokens, and easier to audit. • Minimal boilerplate for servers: you can expose plain Python functions as MCP tools with almost no glue code. • CLI + registry: manage MCP servers, configs, and agents from the CLI; servers can be added/removed without touching agent code.
The goal is to make MCP setups feel more like a composable systems tool than a black-box agent framework.
Repo: https://github.com/poly-mcp/Polymcp PyPI: https://pypi.org/project/polymcp/
I’d love feedback, especially from people already experimenting with MCP, inspectors, or multi-tool agents.