Gelbooru MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GELBOORU_API_KEY | No | Your Gelbooru API Key. Found on your account options page. Optional but recommended to avoid rate limiting. | |
| GELBOORU_USER_ID | No | Your Gelbooru User ID. Found on your account options page. Optional but recommended to avoid rate limiting. | |
| GELBOORU_CACHE_DIR | No | Custom cache folder path for storing analyzed character tag data. | .gelbooru_cache/ |
| GELBOORU_CACHE_TTL | No | Cache lifetime in seconds (default is 24 hours). | 86400 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_postsA | Search Gelbooru posts by tags, page, limit, or ID. Supports all Gelbooru tag syntax: AND (tag1 tag2), OR ({t1~t2}), NOT (-tag), wildcards (tag / tag), meta-tags like rating:safe/questionable/explicit, score:>=N, width:>=N, user:name, sort:random, sort:score:desc, etc. |
| get_deleted_postsC | Retrieve deleted posts. Pass last_id to get everything deleted above that post ID. |
| search_tagsB | Search Gelbooru tags by name, pattern, or ID. Useful for autocomplete, tag counts, and tag type lookup. |
| search_usersC | Search Gelbooru users by name or name pattern. |
| get_commentsC | Retrieve comments for a specific Gelbooru post. |
| get_character_tagsA | Given a character name (e.g. 'misty_(pokemon)'), fetches the top highest-scored general/solo posts across multiple pages and returns the most frequently occurring tags split into three semantic buckets: eye colour/shape, hair colour/style, and other character traits. Each tag includes a frequency score. Results are cached to disk for 24 hours. |
| build_promptA | Given a character name, returns a ready-to-use image-generation prompt string like 'misty (pokemon), green eyes, orange hair, side ponytail, ...'. Internally calls get_character_tags with caching, then assembles the prompt with tags ordered by frequency (eye → hair → other). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: build_prompt generates prompts, get_character_tags fetches character metadata, get_comments retrieves comments, get_deleted_posts accesses deleted content, search_posts searches posts, search_tags searches tags, and search_users searches users. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern using snake_case: build_prompt, get_character_tags, get_comments, get_deleted_posts, search_posts, search_tags, and search_users. The naming is predictable and readable throughout the set.
With 7 tools, the count is well-scoped for a Gelbooru-focused server, covering key operations like searching posts/tags/users, retrieving comments/deleted posts, and building prompts from character data. Each tool earns its place without being excessive or insufficient.
The tool set provides comprehensive coverage for interacting with Gelbooru's content and metadata, including search, retrieval, and prompt generation. Minor gaps exist, such as no tools for uploading posts or managing user accounts, but these are not critical for typical agent workflows and the core operations are well-covered.