Magic MCP vs Picorn MCP — MCP Server Comparison | AllMCPs
Magic MCP vs Picorn MCP
A side-by-side look at the Magic MCP and Picorn MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for developer tools work as a local process; choose Picorn MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Magic MCP when
You need dedicated capabilities in the Developer Tools domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: API key required.
You have the keys it needs: TWENTY_FIRST_API_KEY, API_KEY_21ST.
No tool names declared yet. Check the project README from the listing page.
Picorn MCP tools 32
picorn_capabilitiesList live canvas formats, fonts, layouts, image models, GPU reachability and fair-use limits.
picorn_projects_createCreate a marketing project that can hold many editor files and imported image assets. Keep the returned workspaceProjectId and workspaceProjectKey together; use them when adding every related file.
picorn_projects_inspectList every editor file, imported asset, and the project brand profile with named colors and saved logos or visual references. File entries include their current thumbnail, status, creation URL and canonical /studio/editor?runId=... editorUrl. Always give the user that editorUrl.
picorn_projects_updateUpdate the name, description, or named color scheme of a marketing project, then return its complete file, asset, and brand index.
picorn_design_imageCODEX-ONLY. The calling Codex supplies the complete SVG, including copy and layout. Picorn resolves declared placeholders and renders it through Fabric/SVG. No internal language or design model is called.
picorn_generate_imageGenerate a raw image with self-hosted Z-Image Turbo. Returns an inline preview and public creationUrl.
picorn_generate_vector_assetsUse Picorn's native editor engine: first generate raster artwork with self-hosted Z-Image Turbo on ComfyUI, remove its background, then convert it through the bundled multi-colour SVG converter. Generates five variants, selects the strongest result and returns the top three. Signets also return one layered editor file that displays the three shortlisted SVGs inside the same native project. Use this tool for every newly generated signet and custom icon.
picorn_edit_imageTransform an existing image with Flux 2 Klein. Returns an inline preview and public creationUrl.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. Picorn MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Magic MCP for developer tools work and Picorn MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Magic MCP is listed as a paid service. Auth: api key required. Picorn MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add 21st-dev-magic-mcp and picorn-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 48/100 (Fair) with 16 views, 1 installs and 5,997 GitHub stars. Picorn MCP has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.
picorn_render_svgRender your SVG through Picorn with real typography and declarative image workers. Put placeholder <rect> elements inside the SVG and choose their backend with data-clipart-engine="svg-converter" (fresh ComfyUI image, background removal, then Picorn PNG→SVG vectorisation), data-clipart-engine="z-image-turbo" (raster photo/cutout), or data-clipart-engine="library" (existing vector only). Include data-clipart-prompt; use data-clipart-num-colors="1..7" for svg-converter, and data-clipart-keep-bg="true" for a full scene. Picorn resolves all placeholders internally; never call the admin converter or return generated base64 yourself. Returns an inline preview and public creationUrl.
picorn_editor_import_imageImport image bytes from any external or agent-native image generator into Picorn storage. Pass imageBase64 with or without a data: prefix, then use the returned imageUrl in one or more native image layers. This is the bridge for iterative generator → editor → render workflows.
picorn_editor_create_projectCreate a persistent native Picorn editor project. For a finished static layout, pass svg: a complete SVG containing text/shapes plus declarative data-clipart placeholders. Picorn runs the selected engines in the background, stores the generated assets, converts the SVG into editable native layers, and returns a populated project in one call. Omit svg only when you intentionally want an empty slide for incremental layer operations. Returns projectId, slideId, exact canvas dimensions, and the canonical /studio/editor?runId=... editorUrl that must be included in the final answer.
picorn_editor_create_slideshowCreate, persist and render a complete 1–20 slide Picorn file in one deterministic call from finished agent-authored SVG and/or native editable layers. The calling agent is the only design model: this path does not call /api/generate-svg, Gemini, OpenRouter, or another LLM. Work is bounded before persistence to 50,000,000 total canvas pixels and 1,000 total layers. Fair-use cost is one unit per four slides, rounded up. Returns every persistent render URL, an inline contact-sheet preview, and the canonical editorUrl. Response provenance is modelProvider="calling-agent" and externalLlmCalls=0.