Skip to main content

Documentation Index

Fetch the complete documentation index at: https://kasava.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

When connected via MCP, your AI agent has access to 8 tools, 3 server-side AI agents, and 2 multi-step workflows. The toolset was right-sized in May 2026 (cut from 23 — see ADR-0015) so cacheable data — product graph, work breakdowns, ownership, rationale, health — lives in your local .kasava/ artifact instead, refreshed by kasava sync. Live data (semantic search, customer signals, agents, write surfaces) stays in MCP.

​
Authentication

All MCP connections require a Kasava API key. Create one at Settings → API Keys. The MCP server endpoint is: 
https://api.kasava.dev/v1/mcp/sse

​
Example: Connecting from Claude Code

The Kasava plugin configures this automatically. To do it manually: 
{
  "mcpServers": {
    "kasava": {
      "url": "https://api.kasava.dev/v1/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

​
Example: Connecting from Cursor

{
  "mcpServers": {
    "kasava": {
      "serverUrl": "https://api.kasava.dev/v1/mcp/sse",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

​
Tools (8)

​
code-tool

Search and navigate codebases using Kasava’s symbol graph.
ActionDescriptionKey Parameters
search_symbolsFind symbols by name or patternquery, repositoryId, symbolTypes, limit
get_definitionGet full source of a symbolsymbolName, repositoryId
find_usagesFind all references to a symbolsymbolName, repositoryId, limit
find_dependenciesTrace symbol dependenciessymbolName, repositoryId, maxDepth
get_file / get_filesRead file contentfilePath, repositoryId, branch
get_related_filesWalk dependency graph from a filefilePath, repositoryId
list_filesList files in a pathrepositoryId, path
semantic_searchNatural language code searchquery, repositoryId, limit
search_commentsSearch comments and docstringsquery, repositoryId
search_tech_debtFind TODO/FIXME/HACK markersrepositoryId, limit
find_dead_codeFind unused exported symbolsrepositoryId, limit
find_code_smellsDetect code quality issuesrepositoryId, limit

​
commit-tool

Query commits with semantic analysis.
ActionDescriptionKey Parameters
listList commits with filtersrepositoryId, semanticType, impact, author, dateRange
getGet commit detailssha, repositoryId
hotspotsFind frequently changed filesrepositoryId, limit
changelogGenerate markdown changelogrepositoryId, dateRange

​
search-tool

Unified context-aware search across code, issues, plans, docs, competitors, and comments. Carries plan staleness flags and code references inline.
ActionDescriptionKey Parameters
searchSingle-call multi-corpus searchquery, productId, corpora, limit

​
document-search-tool

Search uploads, plans, customer signals, and product documentation.
ActionDescriptionKey Parameters
search_uploadsSearch uploaded documentsquery, productId, limit
search_plansSearch plan contentquery, productId, limit
search_product_docsSearch indexed documentationquery, productId, limit, minSimilarity
search_signalsSearch customer signalsquery, signalType, urgency, productId

​
competitor-tool

Live competitive intelligence and market analysis.
ActionDescription
get_intelStructured competitor analysis
search_docsSearch competitor documentation
search_trendsMarket trend analysis
get_competitive_intelFull competitive intelligence
get_gong_signalsCompetitor mentions from sales calls

​
entity-analysis-tool

Analyze relationships between code entities (graph traversal).
ParameterTypeDescription
entityTypestringType of entity to analyze
entityIdstringEntity identifier
includeRelatedbooleanInclude related entities
includeImpactbooleanInclude impact analysis
includeGraphbooleanInclude dependency graph
includeExplanationbooleanInclude AI explanation

​
spec-export-tool

Export plans as agent-consumable specifications. Returns the agent-prompt format (condensed, clipboard-ready). For full markdown specs, read .kasava/plans/<slug>.md after kasava sync.
ParameterTypeDescription
planIdstringPlan to export
formatmarkdown | jsonOutput format
includeCodeContextbooleanInclude relevant code references

​
record-decision-tool

Record an agent decision against a plan (“done, deviated because X”). Closes the plan-to-code feedback loop. The only write surface exposed via MCP.
ParameterTypeDescription
planIdstringPlan this decision relates to
decisionTypearchitecture | technology | feature | process | scope
summarystringShort decision summary
rationalestringWhy this decision was made

​
Agents (3)

These agents orchestrate multiple tools for complex queries.
AgentInvoke withPurpose
Code Intelligenceask_codeIntelligenceAgentDeep code analysis, symbol tracing across many files
Product Insightsask_productInsightsAgentProduct health, architecture overview, sprint analytics
Architecture Investigationask_architectureInvestigationAgentArchitecture analysis and recommendations

​
Workflows (2)

WorkflowInvoke withPurpose
Bug Analysisrun_bugAnalysisWorkflowMultimodal bug analysis with code search + AI synthesis
Deep Researchrun_deepResearchWorkflowMulti-step research with web search

​
Usage Examples

Here are natural language prompts and the tools they invoke:
PromptTools used
”How does checkout work in our app?”code-tool.search_symbols → get_definition → find_dependencies
”What competitors are doing with AI features?”competitor-tool.get_competitive_intel
”Show me recent high-impact commits”commit-tool.list (impact: high)
“Find all customer reports about login”document-search-tool.search_signals (signalType: bug_report)
“Research how other companies handle rate limiting”run_deepResearchWorkflow
”Export our auth plan as a starter prompt for an agent”spec-export-tool (format: markdown)
“I’m done with the rate-limit task — record that we used a sliding window”record-decision-tool (type: technology)

​
What’s not in MCP (and where it lives)

These data sources moved out of the MCP toolset in May 2026 — they live in your local .kasava/ artifact (refreshed by kasava sync) or are accessed via CLI / web app.
ConceptWhere it lives now
Product graph (features, layers, tech stack).kasava/graph.json, read via the kasava-context skill or any tool
Work breakdowns.kasava/work-items.json
Plan agent-spec markdown.kasava/plans/<slug>.md (also via kasava plan and spec-export-tool)
File ownershipkasava ownership <file> (CLI)
File rationale (TODO/FIXME + referencing docs)kasava rationale <file> (CLI)
Repository / integration healthWeb app dashboards
Linear / Jira / Asana writesWeb app — Plans → Export to Platform
GitHub issue / PR operationsThe gh CLI; or Linear/Jira/Asana via web export
Long-running deep researchrun_deepResearchWorkflow (workflow) or web app Research surface
Report generationWeb app dashboards
Code diff renderinggit diff