# danbooru-tag-mcp [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/BaixuanZhu/danbooru-tag-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/danbooru-tag-mcp

## Description
Danbooru tag lookup MCP server for AI image generation: tags, aliases, tag profiles, wiki, posts

## Tools
Capabilities this server exposes over MCP:

- **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)
- **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)
- **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…

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "danbooru-tag-mcp": {
    "command": "npx",
    "args": ["-y","danbooru-tag-mcp"],
    "env": {
      "DANBOORU_LOGIN": "",
      "DANBOORU_API_KEY": "",
      "DANBOORU_MCP_NO_BOOTSTRAP": ""
    }
  }
}
```

**Requires environment variables:** `DANBOORU_LOGIN`, `DANBOORU_API_KEY`, `DANBOORU_MCP_NO_BOOTSTRAP` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What danbooru-tag-mcp MCP server does

The danbooru-tag-mcp MCP server gives an MCP client access to Danbooru tag and post data for image-generation workflows. It can identify canonical tag names, distinguish current Danbooru names from WD14 vocabulary names, retrieve descriptions, and inspect how tags appear together on actual posts.

The server exposes seven tools:

- `search_tags` finds matching tags and sorts them by post count. If ordinary results have no posts, it can also return matching WD14 vocabulary names.
- `get_tag_info` returns a tag's category, post count, and `wd14` status: `live`, `tagger_era`, or `unknown`.
- `get_related_tags` finds co-occurring tags while excluding selected meta-category noise.
- `get_tag_alias` maps an alias or misspelling to its canonical form.
- `get_tag_wiki` returns descriptions, multilingual names, and linked tags extracted from a wiki body.
- `search_posts` searches by a space-separated tag combination and returns tags divided into copyright, artist, character, general, and meta categories.
- `get_tag_profile` samples posts for a tag and reports frequent co-tags, ubiquitous corpus terms, and high-lift tag pairs.

## How it works

MCP clients launch the executable as a local command. The server queries Danbooru and returns structured results to the client. Post searches have no rating restriction by default; add a `rating:g`, `rating:s`, `rating:q`, or `rating:e` metatag when the query needs a rating constraint.

A tag profile uses a random sample, defaulting to 200 posts and accepting values from 20 through 200. Its frequency results describe the selected sample, while `top_pairs` ranks combinations by co-occurrence above expected chance. The profile excludes the requested tag and meta tags from its reported combinations.

Requests are throttled to one every 1.5 seconds. Anonymous access is supported, while authenticated requests can receive higher limits and content access. Anonymous or free post searches remain limited to two content tags per query.

## Setup and configuration

The danbooru-tag-mcp MCP server requires Windows 10 or 11 on x64 or ARM64 for the supplied installers. Installation options include a per-user setup executable, a PowerShell installer, or a portable ZIP. The installer places the executable in the user's local application directory or a selected location and registers the directory on the user PATH.

Configure the client with a stdio entry that launches `danbooru-tag-mcp` with no arguments. The executable also supports `upgrade`, `version`, and `help` commands. Building from source requires Go 1.26 or later and GNU Make.

Optional Danbooru credentials use `DANBOORU_LOGIN` and `DANBOORU_API_KEY`. Set both to authenticate requests. `DANBOORU_MCP_NO_BOOTSTRAP`, when non-empty, disables startup PATH registration.

## Limitations and notes

Results depend on the live Danbooru API and its current tag, wiki, and post data. The WD14 status identifies names present in the pinned tagger vocabularies; a `tagger_era` result may require alias lookup because Danbooru has renamed it.

The default lack of a rating filter means post results can include the full population represented by the query. Clients and users should add an explicit rating metatag when that matters. The supplied installation material describes Windows targets; it does not document packaged installers for other operating systems.

_Full upstream README: https://allmcps.com/mcp/danbooru-tag-mcp/readme_