Skip to main content
Glama
Sign In
Heartran

Kanka MCP Server

by Heartran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Kanka MCP Server

No user-submitted related servers found.

    Related Servers

    • kanka-mcp

      torinvdb
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible agents to authenticate to a Kanka account and interact with campaigns, entities (CRUD on all 18 entity types, posts, relations), and full-text search.
      15
      2
      MIT

    • MCP-Kanka

      twistymaze
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with Kanka campaigns through CRUD operations on entities like characters, locations, organizations, and quests, with support for markdown content, batch operations, and efficient synchronization.
      9
      4
      MIT

    • ddb-mcp

      Doogan1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible clients to read D&D Beyond characters, campaigns, and game reference data, with optional opt-in tools for session tracking and character building.
      MIT
    • SagaSmith D&D MCP by SagaSmithAI

      SagaSmith D&D MCPofficial

      SagaSmithAI
      A
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server for Dungeons & Dragons campaign management, combining core runtime with skill and module-generation packs. It enables campaign creation, module generation and import, rule and skill searching via tools, resources, and prompts.
      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

    C2.5/5.0

    Scored across 77 tools

    Disambiguation4/5

    Each entity type has a clear list/get/create/update/delete split, so tool selection is mostly determined by the entity being managed. The generic `search` tool and the broad `list_*`/`get_*` surface add slight overlap, but no two tools appear to do the same job.

    Naming Consistency4/5

    Nearly all tools follow a snake_case verb_noun pattern, such as `create_event` and `delete_calendar`. Minor deviations exist: `search` is a bare verb, and the spelling inconsistency between `list_organisations` and the CRUD tools using `organization` breaks the otherwise predictable naming.

    Tool Count1/5

    77 tools for CRUD across 16 entity types is extremely heavy and well past the 50+ threshold for an oversized surface. The same coverage could be exposed with fewer generic or grouped tools, and this count is likely to overwhelm tool selection.

    Completeness4/5

    Core lifecycle coverage is strong: every major entity type has list/get/create/update/delete operations, avoiding obvious CRUD dead ends. However, campaign-level operations, relations, tags, posts, members, and other Kanka features are absent, so non-CRUD workflows may hit gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources