How do I connect Kuma MCP Server to Claude?

Run `claude mcp add kuma -- npx -y @plumpslabs/kuma` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.

Is Kuma MCP Server free?

The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.

What can Kuma MCP Server do?

Kuma MCP Server documents 13 tools to the agent, including arch_flow, checkpoint, decision. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.

Kuma

Unclaimed

by plumpslabs

Not a plugin for one agent — an infrastructure layer for ALL agents. Works with Claude Code, GitHub Copilot (Codex), Gemini CLI, Cursor, and any MCP-compatible client.

Set up this server

Compare servers My Stack

01 / Choose your client

02 / Before you connect

Authentication is not specified. Check the project instructions before connecting.

Install the runtime required by the project and make it available to your client.

Project instructionsEnvironment variable names (optional)

Use names from the project instructions, separated by commas. Enter names only, never secret values.

03 / Add the configuration

Source: generated from public install instructions

claude mcp add --transport stdio 'kuma' -- 'npx' '-y' '@plumpslabs/kuma'

Run in your terminal after replacing any placeholders.

04 / Check it in your client

Open your client’s MCP settings and confirm the server connects and lists its tools. A copied configuration does not confirm a working connection.

agy-cliai-agentsantigravityclaude-codecursor-idedeveloper-toolsdeveloper-tools-ai-agentgemini-climcpmcp-servermcp-serversmcp-toolsopencode

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

13 of 13 tools

Documented tools (13)

From project documentation. A server handshake does not verify each tool’s description or behavior.

arch_flow

Record architecture flow (max 5 core files)

checkpoint

Labeled snapshot before risky work

decision

Record ADR-style decision with rationale

flow

Read a recorded architecture flow

gotcha

Record bugs/quirks IMMEDIATELY

guard

Detect anti-patterns, drift, runaway loops

history

Why is this file written this way (cross-session trace)

init

Lean project brief + restore session

research

5-step pipeline: cache → graph → scan → impact → decision

research_save

Save research findings to cache

rollback_label

Restore a labeled snapshot

search

Quick lookup of memory + knowledge graph

verify

Auto-run scoped tests after edits

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Kuma MCP Server

How do I connect Kuma MCP Server to Claude?: Run `claude mcp add kuma -- npx -y @plumpslabs/kuma` in Claude Code, or add the same command and arguments under mcpServers in Cursor's mcp.json or Claude Desktop's claude_desktop_config.json, then restart the client. The blocks above are ready to paste.
Is Kuma MCP Server free?: The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Kuma MCP Server do?: Kuma MCP Server documents 13 tools to the agent, including arch_flow, checkpoint, decision. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.