Skip to main content
Glama

Related Servers

Alternatives to wikimedia

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing web search, news search, and X/Twitter search capabilities via HTTP or stdio.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables any MCP-compatible agent to query a local OpenRhyme activity timeline, search history, and issue control commands over stdio while keeping all data on-machine.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Search and read locally-recorded meeting transcripts over stdio. Read-only, no network. Exposes list_sessions, get_session, and search_transcripts to any MCP client.
      50 PyPI
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes a single tool to retrieve Wikipedia articles from local multistream dump files, offering fast offline access with redirect following and fuzzy matching.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Wikipedia MCP server (read-only): search articles, read plain-language summaries or full text, follow links, browse categories, pull references with source URLs, flag missing citations, resolve disambiguation pages, and check revision history and pageview stats — all via the public Wikipedia API.
      51
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM clients to read, search, create, edit, move, protect, and delete wiki pages, upload files, inspect revision history and recent changes, and query extension data through packs for Semantic MediaWiki, Wikibase, Cargo, Bucket, and NeoWiki. Supports multiple wikis as MCP resources with per-wiki configuration, optional OAuth-authenticated writes, stdio or HTTP transports, and paginated, size-capped responses.
      8 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools are clearly separated by resource (Commons files vs Wikipedia articles) and action (search, get, download, list, reference). Two mild overlaps exist: wikimedia_get_file vs wikimedia_reference_file, and wikipedia_get_article vs wikipedia_reference_article, since both pairs resolve the same object and one adds citation output. The descriptions do distinguish metadata retrieval from reference generation, so misselection risk is low but not zero.

    Naming Consistency4/5

    The set follows a consistent verb_noun pattern (list_category, search_media, get_file, download_file, get_article, list_images, reference_article) with a predictable wikimedia_/wikipedia_ domain prefix. The only deviation is wikipedia_search, which omits the noun while its Commons counterpart is wikimedia_search_media, a small inconsistency in an otherwise regular scheme.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each tool maps to a distinct operation in the media/article workflow. There is no obvious filler or redundant tool for the stated scope.

    Completeness4/5

    The surface covers the core lifecycle: search, resolve metadata, download with provenance, and generate citations for Commons files, plus search, fetch, list images, and cite for Wikipedia articles. Minor gaps remain, such as category discovery/traversal beyond listing direct members, and no batch or license-filtered retrieval, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues