Comma

Use Comma with Roo Code

Roo Code's Architect and Ask modes produce documents — plans, audits, explanations — that deserve reviewers, not a scrollback. Attach Comma as a remote MCP server and those modes can publish a page and hand back the link.

Add Comma to Roo Code

Roo reads a global mcp_settings.json (opened from Roo's MCP settings panel) and a project-level .roo/mcp.json. When both define comma, the project file wins.

{
  "mcpServers": {
    "comma": {
      "type": "streamable-http",
      "url": "https://commareports.com/api/mcp",
      "headers": {
        "Authorization": "Bearer comma_sk_…"
      },
      "disabled": false
    }
  }
}

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.

Roo Code gotchas

  • Hyphen, not camelCase. Roo spells it streamable-http; Cline spells it streamableHttp. Copying a Cline block into Roo verbatim gets the type wrong.
  • Keep the token out of .roo/mcp.json in public repos. Use the global file for the token and the project file only for project-specific servers.
  • Scope the publish rule to the modes that write documents — a .roo/rules-architect/ instruction fires for plans and not for every code edit.

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

Roo picks the tool from the request — there are no Roo Code-specific commands to learn.

A workflow that sticks

  1. Ask Roo 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 Roo 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 Roo Code can be revised tomorrow from Claude Code or Cursor, and the link people bookmarked keeps working.

Token shape

  • Lives in mcp_settings.json (user-level) or .roo/mcp.json (project) — don't commit the project file with a real token in it.
  • 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 → and Scoped tokens for AI agents →.

Try it

Add the entry, generate a token, restart Roo Code, 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 →

Related