Skip to main content
Glama

Related Servers

Alternatives to mediawiki-mcp-server

Related Servers

  • A
    license
    B
    quality
    B
    maintenance
    A secure MCP server for interacting with MediaWiki instances, allowing users to search, read, create, and manage wiki content like pages, categories, and files. It supports both public and private wikis with comprehensive authentication for full read and write operations.
    19
    AGPL 3.0
  • 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
    -
  • 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
  • A
    license
    Not graded
    quality
    A
    maintenance
    MCP server that provides secure access to a serverless Markdown wiki on AWS, enabling AI assistants to read, search, and edit pages with space-level permission checks and Bedrock-powered semantic search.
    MIT

TDQS

A4.1/5.0

Scored across 43 tools

Disambiguation4/5

Most tools have clearly distinct purposes with explicit 'NOT FOR' guidance to prevent confusion. Minor overlap exists between mediawiki_get_related and mediawiki_find_similar_pages, and between mediawiki_search and mediawiki_search_and_read, but descriptions clarify when to use each.

Naming Consistency5/5

All tools follow the mediawiki_verb_noun pattern consistently alert. Verbs are action-oriented (get, search, find, create, update, rename, compare) and nouns are specific (page, revision, link, category). Naming is uniform and predictable.

Tool Count2/5

43 tools is significantly more than the recommended 3-15 for a typical server. While the wiki domain is broad, many tools are minor variations (e.g., get_page vs get_page_summary vs get_page_info) that could be consolidated. The count feels excessive and may overwhelm agents.

Completeness5/5

The tool surface covers the full lifecycle: read (get, search, list), create (edit_page, upload_file), update (find_replace, bulk_replace, manage_categories), delete (via edit_page with empty content, move_page), and maintenance (audit, find_broken_links, check_terminology). No obvious gaps for a wiki server.

Maintenance

ActivityActive
ResponsivenessResponsive