mcp-magicpath

MagicPath (mcp-magicpath)

Look up MagicPath components, projects, teams, design systems, and the live web canvas through the magicpath-ai Node CLI from an agent, via Code Mode's UTCP cli transport. MagicPath ships no MCP server; the bridge is the CLI, registered as the manual named magicpath in this repo's .utcp_config.json. The registered surface is read-only on purpose: fourteen tools that only read. The CLI can also write .tsx files into the calling project, install npm packages, and create remote projects and component revisions (add, code, image, create-project, clone), but those are deliberately not registered, so an agent cannot reach them through a tool call. Deep operational detail lives in references/tool-surface.md, references/credential-setup.md, references/mutation-boundary.md, and references/design-authority.md.

Design authority (read before any work). Every MagicPath surface is a design surface: components, themes, CSS variables, fonts, canvas state. This packet therefore loads sk-design unconditionally and operates under the design agent persona resolved from the active runtime's agent directory. The transport retrieves; sk-design decides. Neither the persona nor the pairing widens this packet's authority — the transport's own tool surface stays narrower than the persona's and wins on every conflict. Full contract: references/design-authority.md.

Transport shape (read first). This is a cli transport manual, not an mcp one. The manual command (node .opencode/bin/magicpath-utcp-manual.cjs) emits the UTCP manual that lists the fourteen tools; each tool then runs through node .opencode/bin/magicpath-utcp-exec.cjs, which shells out to the magicpath-ai binary. Code Mode's naming convention is {manual}.{tool}, so the callable form is magicpath.<tool>(...) (for example magicpath.search_components), and discovery names appear dotted as magicpath.<tool>. The tool names have no magicpath_ prefix of their own, so the prefix is applied once, not doubled. Confirm the exact callable with tool_info per session and fail closed on drift.

Calling convention (hard). Inside call_tool_chain, tools are synchronous. Call them directly. Do not use await, do not use top-level await, and do not return a Promise — a returned Promise silently marshals as {} with no error. Plain JavaScript only; TypeScript type annotations fail to parse. A failing command does not throw. It returns the error text or a JSON error object as an ordinary value, so callers must inspect the returned value rather than rely on try/catch.