Doodleworks MCP vs Picorn MCP
A side-by-side look at the Doodleworks 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 Doodleworks 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 Doodleworks MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENAI_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY. - You want tools like
create_illustrations, get_illustration, regenerate_illustration.
Choose Picorn MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
picorn_capabilities, picorn_projects_create, picorn_projects_inspect.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OPENAI_API_KEYGEMINI_API_KEYGOOGLE_API_KEY | None listed |
Tools & capabilities
Doodleworks MCP tools 3
create_illustrationsRender a set of single-idea, hand-drawn Tinku illustrations (each 16:9; an optional 21:9 hero) and open an interactive viewer. Supply one entry per illustration; each `prompt` is a contraption composition + Tinku's action + its exact English annotations — the server applies the Tinku character, the conceptual engine, and the house style. Use this when the user wants hand-drawn illustrations for an article, post, or explainer.get_illustrationReturn the rendered image for one illustration of a previously created set. The viewer calls this for each illustration after create_illustrations so a single tool result never carries the whole set.regenerate_illustrationRe-render a single illustration with the same (or a tweaked) prompt and aspect. Image models are non-deterministic, so this yields a fresh take. Returns the new image in `_meta` for the viewer.
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.
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.
Doodleworks MCP
{
"mcpServers": {
"doodleworks-mcp": {
"command": "npx",
"args": [
"-y",
"doodleworks-mcp"
],
"env": {
"OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE",
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
}
}
}
}
Picorn MCP
{
"mcpServers": {
"picorn-mcp": {
"url": "https://picorn.com/mcp?utm_source=allmcps&utm_medium=mcp_directory&utm_campaign=mcp_directory_2026_08&utm_content=profile"
}
}
}
Frequently asked questions
Doodleworks 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 Doodleworks 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.
Doodleworks MCP has no declared pricing — check the project's own site. 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 doodleworks-mcp and picorn-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Doodleworks MCP has a quality signal of 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Picorn MCP has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.