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,