Kage MCP Server: 62 Tools with Risk Policies

// ALL 62 KAGE TOOLS

READ 43 tools

Read kage_memory_audit Return the repo-local audit trail for explicit memory mutations: capture, feedback, review, supersede, depr... Read kage_branch_overlay Build and return branch overlay metadata: branch, head, merge-base, changed files, and pending packet IDs. Read kage_contributors Build local contributor profiles from git history: commits, recent activity, touched files, modules, owners... Read kage_profile Return a compact project profile for agent orientation: repo totals, languages, top code+memory concepts, k... Read kage_code_graph Query the source-derived codebase graph: files, symbols, imports, calls, routes, tests, package scripts. Th... Read kage_context_slots List repo-local pinned context slots. Pinned slots are small, reviewable facts that Kage includes in recall... Read kage_fetch Fetch the full content of a specific node from the kage knowledge graph. Use after kage_search to get the c... Read kage_graph Query the repo-local Kage knowledge graph. Returns typed, evidence-backed graph facts from entities, edges,... Read kage_list_domains List all domains in the kage knowledge graph with their node counts and top tags. Use to orient before sear... Read kage_pr_check Check whether repo memory, code graph, memory graph, and stale-memory state are ready for merge. Leads with... Read kage_search Search the kage community knowledge graph for gotchas, patterns, configs, and architectural decisions acros... Read kage_validate Validate repo-local Kage memory packets, pending packets, generated indexes, and sensitive-content checks. Read kage_verify_agent Verify that Kage is truly active for the current agent: config, repo policy, indexes, recall, code graph, a... Read kage_verify_citations Verify that a memory packet Read kage_audit Audit whether repo memory and code intelligence are trustworthy: validation, memory inbox, structured conte... Read kage_benchmark Return Kage proof metrics, or set mode=memory_quality / memory_scale for synthetic memory retrieval benchma... Read kage_benchmark_compare Compare the same task on the same repo with and without Kage. Reports estimated baseline discovery tokens/s... Read kage_capabilities Return an evidence-backed Kage memory-system capability audit across repo memory, collaboration/session pro... Read kage_cleanup_candidates Find conservative cleanup candidates from Kage Read kage_decisions Summarize Kage why-memory for a repo: decisions, gotchas, runbooks, conventions, code explanations, path co... Read kage_dependency_path Find how two files are connected in Kage Read kage_graph_insights Return deterministic code graph intelligence: central files, dependency cycles, import communities, and sho... Read kage_graph_visual Export the repo-local Kage knowledge graph as Mermaid flowchart text for visual inspection. Read kage_inbox Return an actionable memory review inbox: pending packets, stale packets, duplicates, missing structured co... Read kage_learning_ledger Return an agent-facing ledger that classifies observed session events into save, ignore, needs-evidence, or... Read kage_memory_access Report which repo-local memory packets have actually been recalled recently. This uses local ignored access... Read kage_memory_handoff Return a teammate/agent handoff queue by combining memory inbox, lifecycle, audit, timeline, and lineage in... Read kage_memory_lifecycle Return a repo-local memory lifecycle report: healthy, hot, cold, stale, disputed, ungrounded, pending, gene... Read kage_memory_lineage Return memory supersession chains so agents can use current replacement packets and keep retired memory as ... Read kage_memory_timeline Return recent repo-memory activity for teammate handoff: added, updated, pending, and deprecated packets wi... Read kage_metrics Return concise Kage adoption and quality metrics: code graph counts, language/parser coverage, memory graph... Read kage_module_health Return local module health scorecards from Kage Read kage_quality Return memory quality metrics: useful memory ratio, duplicate burden, stale/wrong feedback, evidence covera... Read kage_recall Recall repo-local Kage memory from .agent_memory packets. Returns an agent-ready context block plus ranked ... Read kage_registry_recommend Recommend documentation packs, skills, and optional MCPs for this repo based on its package metadata. Recom... Read kage_reviewers Suggest reviewers for target or changed files from local git authorship, recent edits, and code-graph co-ch... Read kage_risk Assess modification risk for files using Kage Read kage_session_replay Return a privacy-preserving replay digest for observed agent sessions: timeline, touched paths, commands, d... Read kage_sessions Summarize local agent observation sessions, durable capture candidates, and next distillation actions witho... Read kage_setup_doctor Audit Kage setup across supported agents, including Claude Code ambient hook readiness when applicable. Read kage_workspace Summarize a local multi-repo workspace: discovered git repos, Kage memory coverage, code graph counts, pack... Read kage_workspace_recall Recall Kage memory across every indexed repo in a local workspace and rank the combined hits. Use for cross... Read kage_xray Return a first-use Repo X-Ray: code structure layers for entry points, core files, risk, tests, memory over...

WRITE 16 tools

Write kage_graph_registry Build a signed graph-registry manifest for generated memory graph, code graph, indexes, metrics, audit, inb... Write kage_structural_index Build the complete cache-backed structural index for large repos. This covers all supported source/config/d... Write kage_observe Store an automatic local observation event from an agent session. Observations are privacy-scanned, dedupli... Write kage_capture Create a repo-local Kage memory packet immediately. Org/global promotion still requires explicit human revi... Write kage_code_index Write external code index artifacts consumed by the code graph. Prefers SCIP when scip-typescript and scip ... Write kage_context_slot_set Create or update a repo-local pinned context slot. Use for durable, high-signal repo guidance that should a... Write kage_distill Distill stored observations for one session into repo-local memory candidates. Org/global promotion still r... Write kage_feedback Record usefulness feedback on an approved repo-local memory packet: helpful, wrong, or stale. Write kage_install_policy Install or update the repo AGENTS.md policy that tells coding agents to use Kage automatically. Write kage_learn Capture an actual reusable learning from the current session as repo-local memory. Prefer this over diff pr... Write kage_memory_reconcile Return agent-owned memory reconciliation work when source files linked to existing memory changed. Agents m... Write kage_pr_summarize Create a PR/branch memory summary from local git diff metadata and write repo-local change memory. Use when... Write kage_propose_from_diff Create or update a branch review summary and repo-local change-memory packet from local git status and diff... Write kage_review_artifact Create a Markdown review artifact summarizing pending memory packets for PR or human review. Write kage_setup_agent Generate MCP/setup instructions for Codex, Claude Code, Cursor, Windsurf, Gemini CLI, OpenCode, Cline, Goos... Write kage_supersede Mark one repo-local memory packet as superseded by a replacement packet and write bidirectional lineage edges.

DESTRUCTIVE 2 tools

Destructive kage_context_slot_delete Delete a repo-local context slot by label. Destructive kage_compact Consolidate repo memory: prune dead citations, deprecate hard-stale packets, and surface near-duplicate clu...

EXECUTE 1 tools

Execute kage_refresh Rebuild repo indexes, code graph, memory graph, metrics, and stale-memory metadata. Agents should run this ...

// RUNNING THIS SERVER

The managed route: connect Kage through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y @kage-core/kage-graph-mcp

// FAQ

How many tools does the Kage MCP server have? +

The Kage MCP server exposes 62 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on Kage tools? +

Route the Kage server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do Kage tools fall into? +

Kage tools are categorised as Read (43), Write (16), Destructive (2), Execute (1). Each category has a recommended default policy.

Enforce policy on every Kage tool call.

Start from Kage, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.