mcp-onepiece
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, error, or silent. Default is info. | info |
| ONEPIECE_WIKI_URL | No | Wiki origin. Default is https://onepiece.fandom.com. | https://onepiece.fandom.com |
| ONEPIECE_MAX_CONCURRENCY | No | Maximum simultaneous requests to the wiki. Default is 4. | 4 |
| ONEPIECE_SPOILER_CHAPTER | No | Default spoiler limit (last chapter read). If unset, no default limit is applied. | |
| ONEPIECE_CACHE_MAX_ENTRIES | No | Cache size bound (LRU). Default is 500. | 500 |
| ONEPIECE_CACHE_TTL_SECONDS | No | How long API responses are cached in memory (in seconds). Default is 3600. The arc catalog is kept for 24 hours. | 3600 |
| ONEPIECE_REQUEST_TIMEOUT_MS | No | Per-request timeout in milliseconds. Default is 15000. | 15000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_wikiA | Full-text search of One Piece Wiki articles. Large articles are split into subpages (e.g. 'Monkey D. Luffy/Abilities and Powers'), and those show up in results too. |
| get_pageA | Readable text of an article, with references, navigation boxes and the infobox removed (use get_infobox for that). For long articles pass |
| get_page_sectionsA | Section headings of an article, with indexes usable as get_page's |
| list_subpagesA | Subpages of an article. Major characters are split into tabs such as '/History', '/Personality and Relationships', '/Abilities and Powers' and '/Misc.'; find them here, then read one with get_page. |
| get_infoboxA | The article's infobox as label → value pairs. For characters: affiliations, occupations, bounty, Devil Fruit, age, birthday, height, debut chapter/episode and voice actors. Devil Fruits, arcs, ships and places have their own fields. Fields outside the main block are prefixed with their group, e.g. 'Devil Fruit – Type'. |
| get_page_categoriesA | Categories an article belongs to: a quick way to see a character's crews, Devil Fruit type, species, Haki and more. |
| get_category_membersB | Articles and subcategories in a category, e.g. 'Straw Hat Pirates Members', 'Logia Devil Fruit Users', 'Male Characters'. |
| get_chapterA | A manga chapter's title, volume, release date, Weekly Shōnen Jump issue, the anime episodes that adapt it, its story arc and a short summary. Blocked when past the spoiler limit. |
| get_episodeA | An anime episode's title, air date, season, opening song, the manga chapters it adapts (empty for filler) and a short summary. Blocked when it adapts chapters past the spoiler limit. |
| get_arcA | A canon story arc's saga, position in the story, chapter/episode/volume ranges, release years and neighbouring arcs. Accepts loose names such as 'wano' or 'Enies Lobby'. |
| list_arcsA | Every canon story arc in order, grouped by saga, with chapter and episode ranges. Also answers 'which arc is chapter N in?' via |
| set_spoiler_limitA | Set the last manga chapter the user has read. Afterwards, chapters, episodes and arcs past it are withheld and article sections about later arcs are removed. Call with no chapter to turn the limit off. Use this whenever the user says how far they are, e.g. 'I'm at chapter 900' or 'I just finished Enies Lobby'. |
| get_spoiler_limitA | The current spoiler limit (last chapter the user has read), or null if none is set. |
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 13 tools
Each tool targets a distinct resource or aspect: search, page content, sections, subpages, infobox, categories, category members, chapters, episodes, arcs, and spoiler settings. Even similar-sounding tools like get_arc vs list_arcs are clearly separated by singular vs list. There is no overlap or ambiguity.
All tools follow a consistent verb_noun pattern with snake_case: search_wiki, get_page, get_page_sections, list_subpages, get_infobox, etc. The naming is uniform and predictable, making it easy for an agent to infer functionality from names.
13 tools is well within the ideal 3-15 range for a focused server. Each tool serves a clear purpose in the wiki domain, from content retrieval to structured data extraction and spoiler control, without redundancy or bloat.
The surface covers the full lifecycle of interacting with the One Piece wiki: searching, reading pages, navigating sections/subpages, extracting infobox data, exploring categories, querying chapters/episodes/arcs, and managing spoiler limits. There are no obvious gaps for the intended use case.