Skip to main content
Glama
cryppadotta

Wizzypedia MCP Server

by cryppadotta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Wizzypedia MCP Server

No user-submitted related servers found.

    Related Servers

    • Wikipedia MCP Server

      Rudra-ravi
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that retrieves information from Wikipedia to provide context to LLMs, allowing users to search articles, get summaries, full content, sections, and links from Wikipedia.
      22
      2,985 PyPI
      297
      MIT

    • WikiMCP

      raydeStar
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for Wiki.js projects that enables full-text search, page retrieval, and page management capabilities. It allows LLMs to interact with wiki content through specialized tools for searching, listing, and creating pages.
      -

    • mediawiki-mcp-server

      shiquda
      F
      license
      B
      quality
      C
      maintenance
      A MCP server that allows you to search and retrieve content on any wiki site using MediaWiki with LLMs 🤖. wikipedia.org, fandom.com, wiki.gg and more sites using Mediawiki are supported!
      2
      27
      -

    • Azure DevOps Wiki MCP Server

      uright
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI agents to interact with Azure DevOps wikis, providing capabilities for content search, page management, and hierarchical structure navigation.
      5
      7 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

    A3.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity: create_page, read_page, update_page handle the page lifecycle, while get_categories, get_page_history, and search_pages provide specific metadata and discovery functions. There is no overlap in functionality that could cause misselection.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_page, get_categories, update_page). The naming is predictable and readable throughout the set, with no deviations in style or convention.

    Tool Count5/5

    With 6 tools, this server is well-scoped for a wiki domain, covering core operations like CRUD for pages, search, and metadata retrieval. Each tool earns its place without feeling thin or bloated, aligning with typical server sizes of 3-15 tools.

    Completeness5/5

    The tool set provides complete coverage for wiki operations: create, read, update for pages (though delete is omitted, which is common in wikis to preserve history), plus search and metadata tools (categories, history). There are no obvious gaps that would cause agent failures in this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources