Skip to main content
Glama
Sign In
bishalw

mcp-onepiece

by bishalw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-onepiece

No user-submitted related servers found.

    Related Servers

    • osrs-wiki-mcp

      SSanderV
      A
      license
      A
      quality
      A
      maintenance
      Provides read-only access to Old School RuneScape Wiki data, returning structured content with source provenance via MCP tools for searching pages, items, monsters, quests, shops, and drop sources.
      10
      12 npm
      MIT

    • bulbapedia-mcp

      XDFrost
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables structured access to Bulbapedia's Pokémon encyclopedia through natural language, including searching pages, retrieving Pokémon data, moves, abilities, items, locations, and wiki metadata via the MediaWiki API.
      124 npm
      MIT

    • MediaWiki MCP Server

      Mehta5259
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to search, read, create, edit, and manage pages, files, categories, and revisions on any wiki running the MediaWiki software, with optional OAuth-authenticated write access. Also exposes extension-specific capabilities such as Wikibase entities and SPARQL queries, Semantic MediaWiki and Cargo queries, and NeoWiki knowledge-graph subjects.
      8 npm
      MIT

    • MediaWiki MCP Server

      giuliokumar4012
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to search, read, compare, and edit pages on any MediaWiki wiki, including multi-wiki setups with OAuth-authenticated writes. It also queries extension data such as Wikibase entities, Semantic MediaWiki and Cargo results, and Bucket Lua queries.
      8 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 13 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources