About danbooru-tag-mcp
danbooru-tag-mcp is a Danbooru tag lookup MCP server for local AI image generation, aimed at image-generation workflows and prompt writers. It provides alias, category, co-occurrence, wiki, and post-tag data, including tag distribution profiles.
Key features
- 01Keyword search and exact tag details
- 02Alias resolution and related-tag lookup
- 03Tag wiki and post search
- 04Post tags grouped by category
- 05Tag co-occurrence profiles and combinations
Use cases
- 01Find canonical tags for image prompts
- 02Check renamed WD14 tag names
- 03Explore tag combinations from posts
- 04Assess common co-occurrences for a tag
MCP support
It exposes seven tag search and lookup tools over stdio for MCP clients; the README also documents a remote Streamable HTTP endpoint.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEdanbooru-tag-mcp
A Danbooru tag lookup MCP (Model Context Protocol) server for local AI image generation: your AI client resolves real Danbooru tags — exact names, aliases, categories, post counts, co-occurrence statistics, wiki descriptions, and the tag lists of real posts — before composing prompts, which noticeably improves tag accuracy in generated images.
Quick start
Install per-user (Windows 10/11, no admin rights):
iwr -useb "https://raw.githubusercontent.com/BaixuanZhu/danbooru-tag-mcp/main/install.ps1" | iex
Point your MCP client at the command:
{
"mcpServers": {
"danbooru-tags": {
"command": "danbooru-tag-mcp",
"args": []
}
}
}
That's it — the client picks up the seven tools below on its next session.
Features
- 7 MCP tools: tag search, exact tag info, related tags, alias resolution, wiki lookup, post search, and tag distribution profiles
- Tag distribution profiles:
get_tag_profilesamples a random page of a big tag's posts and answers what it actually renders as — co-occurring tags by in-sample frequency (corpus constants like1girl/solosplit intoubiquitous), plus characteristic combinations ranked by lift, so a 300k-post tag likearm_upcan be checked against what you actually wanted before it pollutes a prompt - Tag lists back from post search:
search_postsreturns each post's full tag list split by category (copyright/artist/character/general/meta), so mining a few posts reveals which tags naturally go together - Tagger-era tag detection:
get_tag_infoclassifies every name against the pinned WD14 tagger vocabularies (wd14field:live/tagger_era— a tagger-era name Danbooru has since renamed, tryget_tag_alias/unknown), so LoRA card captions stop dead-ending at "tag not found";search_tagsaddswd14_hitsfallback hits when no result carries posts - Uncensored by default:
search_postsapplies no rating filter — results reflect a tag's whole population (arm_up is ~95% g/s/q); add arating:g/s/q/emetatag when you want only R-18 or only all-ages - Self-updating:
danbooru-tag-mcp upgradechecks GitHub Releases, verifies SHA256 and replaces the binary atomically - Zero-config install: per-user installer (setup wizard or one-line PowerShell) that registers the install directory into the user PATH automatically
- Polite API usage: requests are throttled to one per 1.5 seconds; anonymous access works, credentials raise the limits (free/anonymous post searches are still capped at 2 content tags per query)
Install
Requires Windows 10/11 on x64 or ARM64.
Option 1: setup wizard (recommended)
Download danbooru-tag-mcp-windows-<arch>-setup.exe from the
latest release
and double-click it. This installs per-user to
%LOCALAPPDATA%\Programs\danbooru-tag-mcp (no admin rights needed) and
registers the user PATH.
Option 2: one-line PowerShell
iwr -useb "https://raw.githubusercontent.com/BaixuanZhu/danbooru-tag-mcp/main/install.ps1" | iex
Custom install directory:
.\install.ps1 -InstallDir "D:\tools\danbooru-tag-mcp"
Option 3: portable zip
Download danbooru-tag-mcp-windows-<arch>.zip from the
release page,
extract danbooru-tag-mcp.exe anywhere, and run it once — the first run
silently adds its own directory to the user PATH (idempotent).
Option 4: ZCode / Claude Code plugin (auto MCP config)
For ZCode and Claude Code users the MCP configuration can come from a plugin
instead of hand-edited JSON: add this repository as a plugin marketplace and
install danbooru-tag-mcp — the plugin ships the danbooru-tags server
definition, so no client-side config is needed.
- ZCode: Plugin Marketplace → Add →
BaixuanZhu/danbooru-tag-mcp→ install thedanbooru-tag-mcpplugin. - Claude Code:
/plugin install danbooru-tag-mcp --marketplace BaixuanZhu/danbooru-tag-mcp(one step, Claude Code 2.1.275+), or add the marketplace first withclaude plugin marketplace add BaixuanZhu/danbooru-tag-mcpand install from there.
The plugin wires the configuration only — the CLI still has to be on PATH
(install it first via Option 1-3 above), and danbooru-tag-mcp upgrade
keeps it updated independently of the plugin. See
plugins/danbooru-tag-mcp/README.md.
Configure your MCP client
Point your MCP client (Claude Desktop, ZCode, etc.) at the command:
{
"mcpServers": {
"danbooru-tags": {
"command": "danbooru-tag-mcp",
"args": []
}
}
}
The bare command name works because the install directory is on the user PATH; alternatively use the full exe path. ZCode and Claude Code users can skip the manual JSON entirely via Option 4.
Tools
| Tool | Description | Parameters |
|---|---|---|
search_tags | Search tags by keyword, ordered by post count; when no result has posts, adds wd14_hits (WD14 tagger vocab names containing the query) | query (required, e.g. blue hair), limit (default 10) |
get_tag_info | 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) | name (required, e.g. blue_hair) |
get_related_tags | Tags that co-occur with the given tag (meta-category tags like highres are filtered out as noise) | tag (required), limit (default 10) |
get_tag_alias | Resolve an alias or misspelling to its canonical tag (null = input is already canonical) | name (required, e.g. sailor_suit) |
get_tag_wiki | Wiki page of a tag: description, multilingual names, and the [[tag]] links extracted from the body | title or other_names (one required), limit (default 5) |
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 | tags (required, space-separated), limit (default 5) |
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 and the tag itself excluded | tag (required, e.g. arm_up), sample (default 200, range 20-200) |
CLI
danbooru-tag-mcp run the MCP server (what MCP clients launch)
danbooru-tag-mcp upgrade self-update via GitHub Release (SHA256 verified)
danbooru-tag-mcp version print the version
danbooru-tag-mcp help show help
Environment variables
DANBOORU_LOGIN— your Danbooru account name (the login you use on the site). Optional.DANBOORU_API_KEY— your Danbooru API key, generated from the API key section of your Danbooru profile. Optional. When bothDANBOORU_LOGINandDANBOORU_API_KEYare set, every request is sent authenticated with your account (higher rate limits and content access); otherwise the client is anonymous and Danbooru applies lower limits.DANBOORU_MCP_NO_BOOTSTRAP— skip the startup PATH registration when non-empty.
Building from source
Requires Go 1.26+ and GNU Make (bundled with Git Bash):
make test # unit tests
make integration # online smoke test against the live Danbooru API (~1 min)
make build # dev build -> dist/<arch>/ (bootstrap disabled)
make release # portable zip + checksums.txt
make installer # NSIS setup exe (requires makensis: scoop install nsis)
Releases are automated: pushing a v* tag makes GitHub Actions run the test
suite and publish the setup exes, portable zips, and checksums.txt for both
architectures.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.