Skip to main content
Glama
chase-roohms

LegendKeeper MCP

by chase-roohms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to LegendKeeper MCP

No user-submitted related servers found.

    Related Servers

    • mcp-obsidian

      OleksandrKucherenko
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Obsidian vaults via the Local REST API to search notes, retrieve content, and perform semantic searches. It features self-healing multi-URL connectivity and supports both stdio and HTTP transports for flexible deployment.
      125 npm
      13
      MIT

    • Obsidian MCP Server

      igorilic
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Obsidian vaults for creating, reading, searching, and managing notes, daily notes, TODOs, session reports, and backlinks through both stdio and HTTP/SSE transports.
      10
      1,967 npm
      4
      MIT

    • Obsidian Remote MCP Server

      dharmikbhesaniya
      A
      license
      C
      quality
      B
      maintenance
      Connects AI assistants and agents to Obsidian vaults through strongly typed tools and resources for reading, creating, searching, organizing, and analyzing notes, tasks, properties, tags, and knowledge-graph data. Supports secure remote access via stdio or Streamable HTTP/SSE with bearer authentication and path isolation.
      33
      1,967 npm
      MIT

    • KaaS

      davideleclerc3767
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable coding agents to query a self-hosted, LLM-compiled Markdown knowledge base through a single ask tool that answers from whole wiki articles and returns citations back to the source pages. Supports both local stdio and remote streamable-HTTP transports, with no embeddings or vector store involved.
      -
    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 31 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (resources, documents, map features, timeline events each have their own verbs). A few pairs could be confused at a glance — create_resource vs create_resources vs create_from_template, and get_resource vs read_document (metadata vs content) — but the descriptions clearly delineate them.

    Naming Consistency4/5

    Strong verb_noun snake_case pattern dominates (list_projects, create_resource, update_map_feature, delete_timeline_event). Minor deviations are 'search' (bare verb, no noun) and 'api_request' (noun_verb ordering), but overall the convention is predictable.

    Tool Count3/5

    31 tools is on the heavy side, but the domain is genuinely broad — wiki resources, documents (pages/maps/timelines/boards), assets, tags, calendars and members. The count is defensible for that surface, though some document/map/timeline CRUD could arguably be folded together.

    Completeness5/5

    Near-complete lifecycle coverage: full CRUD plus trash/restore for resources, documents, map features and timeline events, plus search, tree browsing, tags, templates, facts, and asset upload. The api_request escape hatch explicitly covers remaining gaps (boards, calendars, invites, block edits).

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources