Studio Ghibli vs Tapcolor
A side-by-side look at the Studio Ghibli and Tapcolor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
TapcolorArt & Culture · Local subprocess (stdio)Browse TapColor coloring categories and collections — for AI assistants.55GoodAuth: api key requiredVerdict: choose Studio Ghibli for art & culture work as a local process; choose Tapcolor for art & culture as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Studio Ghibli when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
TChoose Tapcolor when
- You need dedicated capabilities in the Art & Culture domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TAPCOLOR_API_KEY. - You want tools like
list_categories, list_coloring_pages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Tapcolor | |
|---|---|---|
| Category | Art & Culture | Art & Culture |
| Quality signal | 41/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | TAPCOLOR_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Studio Ghibli | View Tapcolor |
Tools & capabilities
Studio Ghibli tools
No tool names declared yet. Check the project README from the listing page.
Tapcolor tools 2
list_categoriesAll 25 categories with collection & page counts.list_coloring_pagesCollections with optional `category`, `q` (search), `limit`, `offset`.
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.
Studio Ghibli
{
"mcpServers": {
"studio-ghibli": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-studio-ghibli"
]
}
}
}
Tapcolor
{
"mcpServers": {
"tapcolor": {
"command": "npx",
"args": [
"-y",
"@tapcolorapp/mcp"
],
"env": {
"TAPCOLOR_API_KEY": "YOUR_TAPCOLOR_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Studio Ghibli is categorized under Art & Culture and uses a local stdio subprocess. Tapcolor belongs to Art & Culture and uses a local stdio subprocess. Pick Studio Ghibli for art & culture work and Tapcolor for art & culture.
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.
Studio Ghibli has no declared pricing — check the project's own site. Tapcolor is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 studio-ghibli and tapcolor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Studio Ghibli has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Tapcolor has 55/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
