Comma

Use Comma with Cline

Cline does its best work on the long jobs — read the service, trace the retry logic, write it up. That write-up belongs on a page other people can comment on, not in a VS Code side panel. Cline speaks remote MCP with custom headers, so Comma is one entry in its MCP settings.

Add Comma to Cline

In VS Code, open Cline's MCP Servers icon → Configure tab → Configure MCP Servers. That opens cline_mcp_settings.json. The Cline CLI reads ~/.cline/mcp.json with the same shape.

{
  "mcpServers": {
    "comma": {
      "type": "streamableHttp",
      "url": "https://commareports.com/api/mcp",
      "headers": {
        "Authorization": "Bearer comma_sk_…"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

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.

On the Cline CLI, cline mcp opens an interactive wizard that writes the same entry.

Cline gotchas

  • Set type explicitly. A remote entry without "type": "streamableHttp" is treated as legacy SSE, and Comma's endpoint is Streamable HTTP — the server shows as failing to connect.
  • autoApprove is per tool. Leave it empty while you get a feel for it, then add search_reports and read_report — read-only calls are the ones worth skipping the approval click on.
  • Put the standing instruction ("publish documents to Comma, reply with the URL") in .clinerules so it survives new tasks.

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

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

A workflow that sticks

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

Token shape

  • Lives in Cline's MCP settings file, which is user-level — it will not be committed with a repo.
  • 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 Cline, 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