Polyphon's MCP Server Makes Your AI Ensemble a Native Agent Tool

Mon, 23 Mar 2026 19:35:00 -0400

Polyphon just shipped MCP server support, and it reframes what the tool actually is. You’ve been opening it as a UI. Now your coding agent — Claude Code, Cursor, Codex CLI, GitHub Copilot — can call into it directly and broadcast a prompt across your entire Claude + GPT-4o + Gemini ensemble in a single tool call.

The practical win is not just convenience. It is that you can package disagreement: three independent models, each with different priors, applied to the same question at once. Five tools, two CLI flags, one Settings toggle. The SessionEventSink abstraction is why this works without duplicating orchestration logic — desktop UI and headless agent calls run on the same engine.

Where in your workflow would paying for disagreement actually change a decision, rather than just produce a louder answer?

I Built a Tool So AI Models Could Talk to Each Other

Mon, 16 Mar 2026 12:30:00 -0400

Every AI power user I know runs the same manual workaround: ask Claude, ask GPT, copy the interesting parts of each into the other, then try to synthesize what you learned. The models are good. The coordination is not.

I just shipped Polyphon v0.1.0-alpha.2 — a free, local-first desktop app that puts multiple AI voices in the same conversation so they can actually respond to each other. You’re the conductor. They’re the ensemble. Save a group of voices as a composition and reuse it whenever you need that ensemble again.

What should a multi-agent conversation feel like when you’re not building a pipeline — when you just want to think out loud with several models at once?

Ai-Orchestration on Corey Daley

Polyphon's MCP Server Makes Your AI Ensemble a Native Agent Tool

I Built a Tool So AI Models Could Talk to Each Other