# Use Comma with Warp — attach an MCP server to Warp's agent

Canonical: https://commareports.com/mcp/warp
Published: 2026-09-16

> Add Comma to Warp's MCP servers with a url and Authorization header, from Settings or ~/.warp/.mcp.json. Warp's agent can publish terminal work as HTML reports.

# Use Comma with Warp

Warp's agent runs the commands, reads the output, and writes the conclusion. Attach Comma and that conclusion becomes a link — incident timeline, benchmark comparison, dependency audit — rather than a block you copy out of the terminal.

## Add Comma to Warp

**Settings → Agents → MCP servers → + Add**, or edit `~/.warp/.mcp.json` (global) or `.warp/.mcp.json` (project — Warp asks you to approve project servers before they run).

```json
{
  "comma": {
    "url": "https://commareports.com/api/mcp",
    "headers": {
      "Authorization": "Bearer comma_sk_…"
    }
  }
}
```

Replace `comma_sk_…` with a token from **Settings → API tokens → New token** on Comma (or export it as `COMMA_API_TOKEN` where the snippet reads an env var). The default scopes — `reports:write`, `comments:read`, `comments:write` — cover publishing and review.

## Warp gotchas

- **No `mcpServers` wrapper** in Warp's own file — server names sit at the top level.
- **Already configured Comma for Claude Code or Codex?** Warp also picks up servers from `~/.claude.json`, `.mcp.json` and `~/.codex/config.toml`, so it may already be there.
- Project-level servers need an explicit approval in Warp before they start.

## What the agent can do

| Capability                | Tools                                                                    |
| ------------------------- | ------------------------------------------------------------------------ |
| Publish a report          | `create_report`, `update_report`, `create_report_from_url`               |
| Find existing reports     | `list_reports`, `search_reports`, `get_report`, `read_report`            |
| Leave / reply to comments | `add_comment`, `reply_to_comment`, `set_comment_status`, `list_comments` |
| Ask for review, share     | `request_review`, `set_report_sharing`, `get_report_signoffs`            |
| Manage assets             | `upload_report_asset`, `list_report_assets`, `delete_report_asset`       |

Warp's agent picks the tool from the request — there are no Warp-specific commands to learn.

## A workflow that sticks

1. Ask Warp's agent to write up the work as a self-contained HTML report and publish it to Comma. It calls `create_report` and returns a link.
2. Send the link. Reviewers open a rendered page and leave comments anchored to the exact line, cell or chart they mean — no account needed to read a public link.
3. Next session, ask Warp's agent to address the comments. It reads the threads with `list_comments`, ships a revision with `update_report` (same URL), replies, and resolves them.

Reports belong to your workspace, not to the agent. A report published from Warp can be revised tomorrow from Claude Code or Cursor, and the link people bookmarked keeps working.

## Token shape

- Lives in `~/.warp/.mcp.json` or Warp's settings — keep it out of the project-level file.
- Scoped — you choose which actions it can take when you create it.
- Revocable in one click from **Settings → API tokens**; revocation applies immediately to the REST API, the MCP server and any routines the token created.
- Rate-limited per token.

Details in [API tokens →](/docs/api-tokens) and [Scoped tokens for AI agents →](/agents/scoped-tokens-for-ai-agents).

## Try it

Add the entry, generate a token, restart Warp, and ask for a report on something you worked on today. Then leave a comment on it and ask the agent what it sees.

**[Generate a token →](https://commareports.com/settings/tokens)**

### Related

- [Comma MCP server overview](/mcp)
- [Share what Warp produced](/agents/share-warp-output)
- [Use Comma with Claude Code](/mcp/claude-code)
- [Use Comma with Cursor](/mcp/cursor)
- [Where should my AI agent post its work?](/agents/where-should-my-agent-post)