MCP-Kanka
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANKA_TOKEN | Yes | Your Kanka API token | |
| KANKA_CAMPAIGN_ID | Yes | The ID of your Kanka campaign |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_entitiesC | Find entities by search and/or filtering |
| create_entitiesC | Create one or more entities |
| update_entitiesD | Update one or more entities |
| get_entitiesC | Retrieve specific entities by ID with their posts |
| delete_entitiesC | Delete one or more entities |
| create_postsC | Create posts on entities |
| update_postsD | Update existing posts |
| delete_postsC | Delete posts from entities |
| check_entity_updatesC | Check which entity_ids have been modified since last sync |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Kanka Context | Information about Kanka's structure and this MCP server's capabilities |
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity: entity operations (create, get, update, delete, find, check updates) and post operations (create, update, delete) are cleanly separated. The descriptions clearly differentiate between working with entities versus posts, and within entities, each action (check updates, find, get, create, update, delete) targets a specific, non-overlapping function.
All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., create_entities, update_posts). The verbs (check, create, delete, find, get, update) are consistently applied to the appropriate nouns (entities, posts), making the naming highly predictable and readable.
With 9 tools, the count is well-scoped for managing entities and posts in a system like Kanka. Each tool earns its place by covering distinct CRUD operations and additional utilities (like check_entity_updates and find_entities), avoiding bloat while providing comprehensive coverage for the domain.
The tool set offers complete CRUD/lifecycle coverage for both entities and posts, with no obvious gaps. It includes creation, retrieval (get and find), updating, deletion, and synchronization (check updates), ensuring agents can handle all core workflows without dead ends in this domain.