MCP tools — 52 tools the maestro uses to coordinate the team
52 native tools. The maestro spawns, delegates, and syncs the whole team — you don't install anything.
The mesh that makes the team work as a team
Overclock embeds an MCP server — Model Context Protocol — inside the app itself, with 52 native tools (46 core + 6 diagnostic) exposed to any agent as mcp__overclock__*. It's through this mesh that the maestro spawns panes, delegates tasks, receives handoffs, creates missions, and generates media — without you installing or configuring anything.
Each CLI's config is auto-generated and injected on spawn. The agent is born connected; the tools are already there.
How to use it
Open a pane
any agent in the cockpit already sees the 52 tools; nothing to configure.
Ask for work that needs a team
the maestro uses the pane and handoff tools to spawn, brief, and hold each agent accountable.
Watch the mesh at work
panes being born on the grid, tasks on the scoreboard, handoffs coming back — all of it is the tools at work.
What the 52 tools cover
| Group | Examples | What it solves |
|---|---|---|
| Panes | pane_spawn, pane_write, pane_read | Open, brief, and read agents on the grid |
| Handoff | handoff_submit, handoff_list | Structured delivery — the only correct way for an agent to report it's done |
| Missions | mission_create, mission_set_status | Create and manage missions with status and worktree |
| Squad and agents | agent_invoke, squad_spawn, squad_save | Invoke specialists by name and run complete presets |
| Catalog | catalog_install, marketplace_search | Install and discover skills and agents |
| Recipes | recipe_list, recipe_get, recipe_save | The menu of harness formations |
| Cron | cron_create, cron_list, cron_delete | Scheduled recurring execution in a pane |
| Media | image_generate, video_generate, audio_generate, media_providers | Image, video, and audio generation without leaving the environment |
| Memory | memory_write, memory_read | Shared facts that survive the session |
| Observation and diagnostics | app_status, app_screenshot, app_watch | See the app's state — the base for QA that tests the product itself |
What this area has today
52 native toolsshipped
46 core + 6 diagnostic, available as mcp__overclock__* to any agent in the cockpit.
Embedded servershipped
Runs inside the app itself — no external server, no manual config.
Auto-generated configshipped
Each CLI's MCP configuration is written and injected by the app — the agent is born already connected.
Durable handoffsshipped
Agent results persist to a database — they survive an app restart, addressable through history.
Structured handoffshipped
The maestro can require a schema on the result — a delivery outside the format is rejected and redone.
Media tools includedshipped
The 4 image, video, and audio generation tools are part of the 52 — same mesh, same server.
Status straight from the product's brain: shipped = actually in use; partial = exists, with documented limits.
Where this actually gets to work
all squads →App Factory
Backend e frontend em paralelo, contra o contrato — não um contra o outro. App web com dados seed pra você usar no primeiro clique: pico de 8+ panes, 3 gates.
Overclock OriginalAutopilot
Roda de madrugada. Te acorda só se quebrar: automação com script + cron + log + alarme de falha, verificada no horário real — N+1 panes, 3 gates.
Overclock OriginalCinema Site
Rouba o DNA da referência. Entrega uma produção de cinema: site completo com design extraído ao vivo, copy por seção e 6 imagens geradas em paralelo — pico de 9 panes, 2 gates.