Why MCP matters
Without MCP, every AI coding session starts from scratch. The AI reads your code but doesn’t know:- What decisions you’ve made and why
- What the product requirements are
- How the data model is designed
- What conventions your team follows
Available MCP tools
When connected, AI tools can call these Kommit tools:| Tool | Description |
|---|---|
search_memory | Search project memories by semantic similarity |
add_memory | Store a new decision, learning, or preference |
get_project_overview | Get a full snapshot of the project — description, features, tech stack |
get_spec | Retrieve the project specification (canvas nodes and edges) |
get_data_schema | Get the project’s data model definitions |
get_feature | Get details about a specific feature node |
get_tech_stack | Get the project’s technology choices |
list_projects | List all projects in the organization |
How it works
- You generate an API key in Kommit (prefixed
km_) - You add the Kommit MCP server URL to your AI tool’s configuration
- When the AI needs context, it calls Kommit’s MCP tools
- Kommit authenticates the request, resolves the project, and returns relevant data