Cool MCP Server

Signed, cited, replayable workflows for Claude, Codex, Gemini, DeepSeek, and other agents.

Local serverstdioTypeScript

What is the Cool MCP server?

Signed, cited, replayable workflows for Claude, Codex, Gemini, DeepSeek, and other agents. The cool mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

You may already use an AI coding agent — a tool like claude, codex, or gemini that reads your code and answers questions about it. The answer comes back as a chat message. Chat is easy to lose, and hard to check.

Adding it to your client

The server ships on npm as cool-workflow, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Its toolset

Everything the assistant can do here goes through one of these:

  • Commitment — What it means for you
  • Workflow — What it produces
  • architecture-review — Map a repo, rank risks, and back every claim with file:line evidence
  • pr-review-fix-ci — Review a PR or branch, work out why CI fails, and propose + verify fixes
  • research-synthesis — Answer a question over a local folder of files — your docs, notes, or papers
  • release-cut — Run a gated, reviewed release with dry-run evidence
  • Problem — Fix
  • Place — What it is

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the cool mcp server does with a few real requests.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Cool's toolset — Commitment, Workflow, architecture-review and 5 more — is a fair guide to whether it matches your workflow. It is maintained by coo1white; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Cool's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Available tools

ToolWhat it does
CommitmentWhat it means for you
WorkflowWhat it produces
architecture-reviewMap a repo, rank risks, and back every claim with file:line evidence
pr-review-fix-ciReview a PR or branch, work out why CI fails, and propose + verify fixes
research-synthesisAnswer a question over a local folder of files — your docs, notes, or papers
release-cutRun a gated, reviewed release with dry-run evidence
ProblemFix
PlaceWhat it is

How to install the Cool MCP server

{
  "mcpServers": {
    "cool-workflow": {
      "command": "npx",
      "args": ["-y", "cool-workflow"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use Cool to Commitment.
  • Use Cool to Workflow.
  • Use Cool to architecture-review.

Frequently asked questions

It connects Cool to MCP-compatible AI assistants such as Claude and Cursor, exposing 8 tools (Commitment, Workflow, architecture-review, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cool directly.