Skip to main content
Glama
shiquda

mediawiki-mcp-server

by shiquda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mediawiki-mcp-server

No user-submitted related servers found.

    Related Servers

    • wikipedia-mcp

      LLLeoLi
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that gives LLMs access to Wikipedia, supporting search, article retrieval, summaries, sections, and related topics across multiple languages and language variants.
      22
      MIT

    • wiki-loop-mcp

      Prometheus-AGS
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides tools to add to, search, and manage a wiki knowledge base, enabling AI chat tools to contribute and retrieve information from the wiki via natural language prompts.
      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.
      -

    • LLM Wiki MCP

      jlnkrth
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.
      18 npm
      1
      MIT

    • Athena MCP

      jannismilz
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets AI assistants search, read, and write to a Wiki.js personal wiki, enabling persistent knowledge management through Markdown pages.
      181 npm
      2
      Apache 2.0
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: get_page retrieves specific page content by title, while search finds pages matching a query. There is no overlap in functionality, making it easy for an agent to select the correct tool based on the task.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (get_page and search, where search implies 'search_pages'). The naming is simple, predictable, and uses snake_case uniformly, providing clear readability.

    Tool Count2/5

    With only 2 tools, the server feels thin for a MediaWiki domain, lacking essential operations like creating, updating, or deleting pages. While get_page and search cover basic retrieval, the scope is incomplete, making it borderline too few for practical use.

    Completeness2/5

    The tool surface is severely incomplete for a MediaWiki server, missing core CRUD operations (e.g., create_page, update_page, delete_page) and other common actions like listing categories or handling user interactions. This will likely cause agent failures in broader workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources