MCP Kanka MCP Server

MCP (Model Context Protocol) server for Kanka API integration. This server provides AI assistants with tools to interact with Kanka campaigns, enabling CRUD operations on various entity types like characters, locations, organizations, and. That is what the mcp kanka mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• Entity Management — Create, read, update, and delete Kanka entities
• Search & Filter — Search entities by name with partial matching, filter by type/tags/date
• Batch Operations — Process multiple entities in a single request
• Posts Management — Create, update, and delete posts (notes) on entities
• Markdown Support — Automatic conversion between Markdown and HTML with entity mention preservation
• Type Safety — Full type hints and validation

The tools it exposes

The server publishes 10 tools. What each one is for:

• find_entities — Search and filter entities with comprehensive options and sync metadata
• create_entities — The create_entities tool exposed by this server
• update_entities — The update_entities tool exposed by this server
• get_entities — The get_entities tool exposed by this server
• delete_entities — The delete_entities tool exposed by this server
• check_entity_updates — Efficiently check which entities have been modified since last sync
• create_posts — The create_posts tool exposed by this server
• update_posts — The update_posts tool exposed by this server
• delete_posts — The delete_posts tool exposed by this server
• Setup — The Setup tool exposed by this server

What it needs from you

Configuration is passed through the environment: KANKA_TOKEN, KANKA_CAMPAIGN_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.10 or higher (3.13.5 recommended) - Kanka API token and campaign ID

Getting it running

mcp-kanka on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Kanka's toolset — find_entities, create_entities, update_entities and 7 more — is a fair guide to whether it matches your workflow. It is maintained by ervwalter; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Kanka.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.