Magic MCP vs Danbooru Tag MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Magic MCP vs Danbooru Tag MCP
In-depth architectural comparison of the Magic MCP and Danbooru Tag MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Magic MCP
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Danbooru Tag MCP
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Magic MCP if you need specialized Developer Tools tools running via a local process. Choose Danbooru Tag MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Magic MCP when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Paid Service).
You have access to required keys: TWENTY_FIRST_API_KEY, API_KEY_21ST.
Magic MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Danbooru Tag MCP belongs to Developer Tools using local stdio subprocess. Select Magic MCP when you need capabilities focused on developer tools and Danbooru Tag MCP when you require tools for developer tools.
Exact info for one tag (category, post count), plus a `wd14` verdict: `live` (current Danbooru), `tagger_era` (WD14 tagger vocab only, likely renamed — see `get_tag_alias`), `unknown` (neither)
get_related_tags
Tags that co-occur with the given tag (meta-category tags like `highres` are filtered out as noise)
get_tag_alias
Resolve an alias or misspelling to its canonical tag (`null` = input is already canonical)
get_tag_wiki
Wiki page of a tag: description, multilingual names, and the `[[tag]]` links extracted from the body
search_posts
Search posts by a tag combination, no rating filter by default (add a `rating:g/s/q/e` metatag to narrow). Each post carries `tags` split by category: `copyright` / `artist` / `character` / `general` / `meta
get_tag_profile
Distribution profile of one tag from a random post sample (default 200 posts, whole population — no rating filter): `co_tags` ordered by in-sample frequency, `ubiquitous` corpus constants (`freq >= 0.5`), `top_pairs` characteristic combinations ranked by lift (co-occurrence above chance). Meta tags…