Use MagicPath through the magicpath-ai CLI to search UI components, inspect source, install React and TypeScript components into applications, work with team projects and themes, and create or edit canvas components from local code.
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · api.magicpath.ai
42tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://api.magicpath.ai/mcp
Skill page: https://www.mcpbundles.com/skills/magicpath-mcp-e1be04e9d0
Explore capabilities (42)
read 16
write 9
Showing 25 of 42
Showing 25 of 42 tools from the public preview. Connect the server to inspect the full live tool list.
Get9
List5
Create2
Other capabilities9
Get API quota
read
get_api_quota
Read the effective billing owner, remaining external-agent API calls, reset time, and charging rules. One prompt may make many tool calls. This lookup consumes one API call and requires remaining quota; the returned balance includes this call.
Get API quota — Read the effective billing owner, remaining external-agent API calls, reset time, and charging rules. One prompt may make many tool calls. This lookup consumes one API call and requires remaining quota; the returned balance includes this call.
Get MagicPath context — Return the authenticated user, teams, MCP connection details, and CLI parity map.
List teams — List MagicPath teams the authenticated user belongs to.
List team members — List the users and roles in one accessible MagicPath team.
List projects — List personal and team MagicPath projects, including ownership and component counts.
Get project — Look up one MagicPath project by id: name, owner (personal or team), your role, live component count, timestamps, and the editor URL. Use it to confirm a project id taken from a URL, a share link, or get_active_projects before listing its components or starting a code session. A project you cannot access reads as not found.
Create project — Create a named personal or team MagicPath project.
List project components — List components in an accessible project with revision and preview metadata.
Search components — Search accessible MagicPath components by display name or generated name.
List themes — List accessible MagicPath themes/design systems for a personal or team workspace.
Get theme — Return a complete accessible MagicPath theme/design-system definition.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Use MagicPath through the magicpath-ai CLI to search UI components, inspect source, install React and TypeScript components into applications, work with team projects and themes, and create or edit canvas components from local code.
How do I connect MagicPath to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
How many tools does MagicPath provide?
Operate this server?
Request removal if you do not want MagicPath listed here, or claim the listing if you want to manage it on MCPBundles.
Operate MagicPath?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
— Return projects currently open in the authenticated user’s MagicPath web canvas sessions.
Get canvas context — Read the shapes on a project canvas: position, size, rotation, stacking index, parent — and what each one is. text is the label written on the shape (wireframe copy, sticky notes, annotations), style is its colour and fill, image shapes carry imageId and component shapes carry componentId with the revision the canvas is showing. Read that text before designing from a wireframe rather than inventing copy. Pass view: "tree" to nest each frame's and group's children inside it, which is how a wirefr
Move, resize or lock canvas shapes — Set position, size, rotation or lock state on existing shapes in one atomic change. Only use when the user asked to move, resize, rotate or lock canvas shapes. Component and image shapes accept geometry only — their content is owned by MagicPath and changed through the component and image tools. Prefer arrange_canvas_shapes when the intent is aligning or laying out rather than exact coordinates.
Align, distribute or lay out canvas shapes — Align, distribute or lay out shapes without computing coordinates yourself: MagicPath measures the shapes and does the arithmetic. distribute_* evens the gaps between the outermost two shapes; grid/row/column repack from the top-left of the current selection using per-row and per-column sizes so mixed-size shapes do not overlap. Shapes must share a parent; any that do not are reported back untouched.
Change canvas stacking order — Change which shapes draw on top. front/back move shapes past all their siblings; forward/backward step one position. Stacking is per parent, so shapes inside different frames are ordered within their own frame.
Group, ungroup or frame canvas shapes — Combine shapes into a group, wrap them in a named frame, or take a group/frame apart. group keeps shapes exactly where they are; frame draws a titled container with padding around them. ungroup lifts children back out and removes the container. Components and images can be grouped — their position and parent survive canvas rebuilds.
Delete canvas shapes — Delete native canvas shapes — wireframe boxes, text, notes, arrows, lines, frames and groups. Component and image shapes are refused: the canvas is rebuilt from those entities, so a delete here would reappear on next open. Deleting a frame or group keeps its children and lifts them out rather than removing content that was not named. Only use when the user asked to delete something.
Create native canvas shapes — Draw native tldraw shapes on the canvas for wireframes, diagrams, labels and annotations: geo boxes (rectangle, ellipse, diamond and the rest), text, sticky notes, arrows, lines and frames. Send ONE STEP of a drawing per call — the frame, then a region, then the contents of that region, roughly 3-8 shapes each — rather than composing a whole layout and sending it at once: your cursor is visible on the canvas and the user is watching it build. Shapes within a call land together and stack in the o
Restyle canvas shapes — Change appearance or label text on native canvas shapes: color, fill, dash, size, font, alignment, geo kind, arrowheads, frame name. Component and image shapes are refused — their appearance comes from their content. Size and position belong to transform_canvas_shapes.
Get canvas selection — Read what the user has selected right now on their open MagicPath canvases. shapes is the full live selection — wireframe boxes, text, notes, frames (with their children nested inside) — each with its label text, alongside the components and images lists. Call this before asking for an id, and whenever the user says "this", "selected", or "here". Build from the selection's own text rather than inventing copy. To use a selected image in component code, pass its imageId/shapeId to start_component_
Get share URL — Return a view/share URL for a project id, a component id, or a component's generatedName. The identifier is resolved, so an id that does not exist fails rather than returning a guessed link. The host may open the URL.
Inspect component source — Return cleaned source, utilities, dependencies, import statement, and JSX usage for a MagicPath component.
Plan component installation — Return all files, dependencies, imports, usage, and host actions needed to install one or more MagicPath components locally. This server cannot write the host filesystem.
Start component coding — Immediately create the pending canvas state and visible agent presence for an edit (componentId) or create (optional projectId), before research. Omit both ids to create a project. Retain an idempotencyKey; reuse it with identical arguments after a lost response, or recover_component_code_session. At most 10 open unsubmitted sessions per caller per project; prefer batches of 2–3 and retain each result. Pass codeSessionId to submit_component_code; never choose revision ids. Branch on filesInlined
Showing the first 25 tools — full list and schemas: Directory API.
MCPBundles probed 42 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does MagicPath require?
MagicPath may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.