Luw.ai vs Doodleworks MCP
A side-by-side look at the Luw.ai and Doodleworks MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Luw.ai for developer tools work as a local process; choose Doodleworks MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Luw.ai when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LUW_API_KEY.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 36/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LUW_API_KEY | OPENAI_API_KEYGEMINI_API_KEYGOOGLE_API_KEY |
Tools & capabilities
Luw.ai tools
No tool names declared yet. Check the project README from the listing page.
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.
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.
Luw.ai
{
"mcpServers": {
"luw-ai": {
"command": "npx",
"args": [
"-y",
"@luw-ai/mcp"
],
"env": {
"LUW_API_KEY": "YOUR_LUW_API_KEY_HERE"
}
}
}
}
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"
}
}
}
}
Frequently asked questions
Luw.ai is categorized under Developer Tools and uses a local stdio subprocess. Doodleworks MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Luw.ai for developer tools work and Doodleworks 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.
Luw.ai has no declared pricing — check the project's own site. Doodleworks MCP has no declared pricing — check the project's own site. 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 luw-ai and doodleworks-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Luw.ai has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Doodleworks MCP has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
