Maestro orchestrates AI agents across all your projects. Shared knowledge, codebase scanning, dependency graphs, and autonomous builds — all from inside Claude Code.
You talk to Claude Code. Claude Code talks to Maestro. Maestro coordinates everything else — agents, knowledge, code graphs, builds.
Six capabilities, one MCP connection. No dashboards, no context switching.
Index any repo with tree-sitter. Search symbols, trace callers and callees, and run transitive impact analysis before you change a line.
Semantic search across every project's code, docs, patterns, and decisions. pgvector embeddings so you find answers, not just keywords.
Dependency graphs with circular detection. Ask "does any project already handle SAML?" and get an answer across your entire stack.
Planner, builder, tester, reviewer, docs, bug hunter, frontend, and discovery. Specialized agents collaborate on threads with evolving skills.
File a request, approve a plan, and agents create branches, write code, run tests, and open pull requests. You review, they execute.
Projects declare what they can do — auth, APIs, data, UI, infra. Before building something new, Maestro checks if it already exists.
Index your repos. Search every symbol. Trace the blast radius of any change before you make it.
Functions, classes, methods, interfaces, enums — all indexed and searchable. Find what you need across every project, instantly.
Trace callers, callees, and transitive dependencies. See exactly what breaks if you refactor a function — across projects.
File a request. Agents triage, plan, build, test, and review — each with specialized skills that improve over time.
you > File a feature request for maestro: add rate limiting
to the /api/search endpoint
claude> maestro.file_request(
kind="feature",
title="Rate limit /api/search",
project="api-service"
)
Thread #247 filed. Planner agent assigned.
Suggested approach uses existing rate-limit
middleware from auth-library (found via KB).
Every feature is an MCP tool. No web dashboard, no context switching. Just talk to Claude.
Paste this into your Claude Code chat:
Add an MCP server called "maestro" with URL https://maestromojo.com/mcp
Tell Claude to register you:
Register me with Maestro using your@email.com
Check your email for the code, then:
Verify my Maestro code: XXXXXX
Not a separate app. Maestro lives inside your Claude Code session as a tool, right where you already work.
Dependency graphs and shared knowledge mean Maestro knows your Library B already has SAML before you build it again.
Agent skills track success rates and refine over time. The more your team uses Maestro, the better it gets.
Not just docs — Maestro indexes your actual code. Symbols, relationships, and impact analysis across your entire stack.