HN Showcase
Back to browse
GitHub Repository

Polymcp provides a simple and efficient way to interact with MCP servers using custom agents

171 starsTypeScript

PolyClaw – An Autonomous Docker-First MCP Agent for PolyMCP

by justvugg·Feb 16, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidNiche GemShip It
The Take

PolyClaw is a practical, infrastructure-aware twist on agent frameworks: it plans multi-step jobs, orchestrates MCP tools, and can spin up MCP servers on the fly while keeping execution Docker-first for isolation. The repo ships both Python and TypeScript SDKs, an Inspector app, runnable examples and a CLI example using Ollama — so it’s more than a toy. It doesn’t reinvent the agent space (AutoGPT/OpenClaw cousins exist), but if you need agents that create and manage real infra safely, this is a useful, pragmatic toolkit.

Target Audience

Platform engineers, DevOps/backend developers, SREs and ML engineers who need automated, infra-aware workflow orchestration

Post Description

I built PolyClaw, an OpenClaw-inspired autonomous agent for the PolyMCP ecosystem.

PolyClaw doesn’t just call tools. It plans, executes, adapts — and creates MCP servers when needed.

It’s designed for real multi-step, production workflows where agents must orchestrate tools, spin up infrastructure, recover from errors, and deliver complete results end-to-end.

⸻

What PolyClaw Does • Plans complex multi-step tasks • Executes and orchestrates MCP tools dynamically • Adapts when steps fail or context changes • Creates and connects MCP servers on the fly • Runs Docker-first for safety and isolation • Built with Python and TypeScript

PolyClaw is not just a tool caller — it’s an infrastructure-aware agent.

⸻

Run PolyClaw with Ollama

You can launch PolyClaw directly from the PolyMCP CLI:

polymcp agent run \ --type polyclaw \ --query "Build a sales reporting pipeline and test it end-to-end" \ --model minimax-m2.5:cloud \ --verbose

What happens behind the scenes: 1. The agent decomposes the task. 2. It determines which MCP tools are required. 3. It spins up or connects to MCP servers. 4. It executes steps in sequence (or parallel when needed). 5. It validates outputs. 6. It adapts if something fails. 7. It returns a complete result.

All containerized. All isolated.

⸻

Why This Matters

Most AI agents: • Call tools statically • Assume infrastructure already exists • Break on multi-step failure

PolyClaw: • Builds the infrastructure it needs • Orchestrates across multiple MCP servers • Handles retries and adaptive planning • Is safe to run in Dockerized environments

This makes it viable for: • Enterprise workflows • DevOps automation • Data pipelines • Internal tooling orchestration • Complex multi-tool reasoning tasks

PolyClaw turns PolyMCP from simple tool exposure only with Polyagent e unifiendpolyagent or codeagent but turn into full autonomous orchestration agent too.

Repo: https://github.com/poly-mcp/PolyMCP

Happy to answer questions,

Similar Projects

Developer Tools●●Solid

PolyMCP – MCP Tools, Autonomous Agents, and Orchestration

It makes a smart, practical bet: let existing Python functions become agent-ready tools by turning type hints into structured tool schemas with validation and HTTP endpoints, so you don't rewrite logic to expose it to agents. The included PolyClaw agent and discovery/orchestration features sound useful for multi-service workflows, but the space is crowded (LangChain/AutoGPT/etc.), so what matters next is demos showing robust orchestration, failure handling, and provider integrations.

Niche GemShip It
justvugg
203mo ago