Skip to main content
Glama
Sign In
freeqaz

shared-wiki-mcp

by freeqaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to shared-wiki-mcp

No user-submitted related servers found.

    Related Servers

    • obsidian_shared_memory

      nhyxb
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI agents to share a locally controlled long-term knowledge base of Markdown notes, allowing them to retrieve, add, update, and remove preferences, decisions, and experiences. It supports cross-agent recall and version-aware changes while keeping the notes readable and editable outside the agent.
      MIT

    • graphmory-mcp

      Grunte12
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and read Markdown notes by keyword, meaning and links, with cited recall and honest no-match results. It also supports guarded, evidence-checked memory writes with receipts, conflict handling and lifecycle-aware filtering.
      MIT
    • eigma-mcp by eigma-app

      eigma-mcpofficial

      eigma-app
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to turn conversations into a searchable personal wiki, read and organize pages, and propose edits such as merges, translations, and fact-checks as reviewable changesets.
      2
      MIT

    • MCP Notes Server

      sixbenzene
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage Markdown notes via the Model Context Protocol, supporting creation, editing, searching, and conflict detection.
      MIT

    • mysharedbrain

      hampusadamsson
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to manage a markdown vault wiki by creating, reading, updating, deleting, moving, and searching notes, as well as giving feedback and asking questions with missed information logged for later retrieval.
      21
      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

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool targets a distinct operation: search for discovery, read for a single note's body/metadata, context for bounded multi-source excerpts, changes for a time-based delta, capture for inbox writes, propose for replacement drafts, review_queue for ranking open questions. The only soft overlap is wiki_search vs wiki_context (both return excerpts), but the descriptions clarify that one is ranked retrieval and the other is question-scoped gathering.

    Naming Consistency4/5

    All seven tools share the wiki_ prefix and snake_case, giving a predictable namespace. However, the second element mixes verbs (search, read, capture, propose) with nouns (review_queue, changes, context), so the verb_noun pattern is not uniformly applied.

    Tool Count5/5

    Seven tools is a tight, well-scoped surface for a shared wiki: retrieval, inspection, review, change tracking, and two write paths. Every tool maps to a real workflow step with no filler.

    Completeness3/5

    Read/discovery/write-capture are covered, but two lifecycle paths dead-end: wiki_propose creates a proposed replacement with no tool to list, accept, or reject proposals, and wiki_review_queue surfaces open questions with no tool to answer or resolve them. Agents can work around this by reading and capturing notes, but the review/proposal loop is incomplete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources