Comma

Claude Code plugin

The plugin layers slash commands and an auto-triggered skill on top of Comma's MCP server, so publishing from a Claude Code session is one command instead of a prompt.

Install

curl -fsSL https://commareports.com/install.sh | bash

Windows (PowerShell):

iwr -useb https://commareports.com/install.ps1 | iex

The installer adds Comma's plugin marketplace, installs the comma plugin, prompts for a comma_sk_… API token (Settings → API tokens in the app), and writes it to ~/.config/comma/env with mode 0600. No sudo, no binary downloads — it only invokes the claude CLI you already have. Restart Claude Code afterwards so it picks up the MCP attachment.

Prefer not to curl-pipe? The manual path is three commands:

claude plugin marketplace add comma/comma
claude plugin install comma@comma
export COMMA_API_TOKEN=comma_sk_your_token_here

Slash commands

Command What it does
/comma-publish [title] Publishes the assistant's most recent reply as an HTML report; returns the share URL.
/comma-publish-last [title] Alias for /comma-publish.
/comma-search <query> Full-text search across your reports (title + body + description).
/comma-link <report_id> Resolves a report id to its title + share URL.
/comma-routine [description] Lists recent reports or kicks off a review on one.
/comma-review <file> Opens a local HTML/markdown file in your browser, lets you leave anchored comments, then feeds them back to Claude as structured feedback so it edits the file in place.

There's also a skill, publish-as-report, that triggers automatically when you say things like "publish this to Comma" — no slash command needed.

Security posture

  • Each slash command is scoped via allowed-tools to the single mcp__comma__* tool it needs.
  • The token lives in your environment, not in the plugin; revoke it from Settings → API tokens and every surface (plugin, MCP, REST) is cut off at once.
  • Scope the token down — reports:write + comments:read + comments:write covers the whole publish-and-respond loop.

Not using Claude Code?

The plugin is convenience, not a requirement. Cursor, Codex, and Claude Desktop attach to the same MCP server directly — see MCP server → — and anything that can curl can use the REST API →.