Summary

Complete coverage, at the cost of a large tool list.

Every entity type gets the same five operations, which makes the tool names predictable and means nothing in your campaign is out of reach. The trade is size: 82 tool definitions ride along in every turn, so this is a server to enable while you are working on a campaign rather than one to leave on permanently. Note that the delete tools are real deletes against your live campaign — there is no dry run.

What it is

A local stdio MCP server for the Kanka worldbuilding API. It runs on your machine and talks to Kanka with your API token, exposing 82 tools that cover the campaign entity types Kanka supports rather than a curated subset.

What you get

Your campaigns listed, and search across the entities inside one — `list_campaigns`, `search`
Full create, read, update and delete on each entity type — Character, Location, Family, Organization, Item, Note, Event, Calendar, Timeline, Creature, Race, Quest, Map, Journal, Ability and Entity — with the same five operations named the same way on every one, so the tool list is predictable once you have seen one type
82 tools in total, which is what "the whole API surface" costs in context — worth knowing before you enable it alongside other servers

Requirements

A Kanka API token from kanka.io/en/settings/api, passed as `KANKA_API_TOKEN`. Node.js 20+. The npm package is `kanka-mcp` (2.1.1 in package.json) with a `kanka-mcp` binary; run it from a clone with `npm install` and point your client at `index.js` by absolute path, or install globally and call the binary. On Windows use forward slashes or escaped backslashes in the path, and restart the client after editing its config.