kanka-mcp
Related Servers
Alternatives to kanka-mcp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceEnables local interaction with the Kanka worldbuilding API via MCP, supporting CRUD operations on characters, locations, and other worldbuilding entities, as well as campaign listing and search.77-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Kanka worldbuilding campaigns, characters, locations, posts, notes, and journals through the Kanka API.MIT
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceEnables MCP-compatible clients to manage AI agent teams, including agents, Kanban issues, projects, goals, approvals, budgets, and raw API access.30MIT
- AlicenseNot gradedqualityAmaintenanceEnables search, content creation, weblink saving, and knowledge base analysis with Capacities through any MCP-compatible client.7MIT
- AlicenseBqualityCmaintenanceEnables 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.94MIT
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes (e.g., create vs. update vs. delete, search vs. full text search vs. list). However, kanka_search and kanka_full_text_search could be confused if descriptions are overlooked, and kanka_list_entities overlaps slightly with browse/search capabilities.
Tools generally follow a 'kanka_verb_noun' pattern, but 'kanka_posts' and 'kanka_relations' are nouns only, breaking consistency. The use of 'full_text_search' with underscores is fine, but the mix of verbs and bare nouns is noticeable.
With 15 tools, the server covers authentication, campaign management, entity CRUD, posts, relations, search, and schema discovery without feeling bloated. Each tool addresses a distinct need, and the count is appropriate for the domain.
The tool surface covers essential CRUD for entities, posts, and relations, plus search and auth. Minor gaps: there is no tool to list entity types or manage campaigns beyond fetching metadata, but these are not critical for typical workflows.