Comma

Use Comma with GitHub Copilot CLI

Copilot CLI already has the GitHub MCP server for issues and PRs. Some work doesn't fit a PR comment — a coverage review, a dependency audit, a long investigation. Add Comma and Copilot publishes those as a page with anchored comments, then links it wherever you want.

Add Comma to GitHub Copilot CLI

User config: ~/.copilot/mcp-config.json. Project config: .mcp.json at the repo root, or .github/mcp.json.

{
  "mcpServers": {
    "comma": {
      "type": "http",
      "url": "https://commareports.com/api/mcp",
      "headers": {
        "Authorization": "Bearer comma_sk_…"
      },
      "tools": ["*"]
    }
  }
}

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.

One line:

copilot mcp add --transport http --header "Authorization: Bearer comma_sk_…" comma https://commareports.com/api/mcp

Inside a session, /mcp add walks through the same fields, including headers.

GitHub Copilot CLI gotchas

  • tools: ["*"] exposes every Comma tool. List specific names (["create_report", "update_report"]) for a publish-only setup.
  • Don't commit the token in .mcp.json. Use the user-level config for anything with a credential in it.
  • Pair it with the GitHub MCP server: Copilot publishes the report to Comma, then links the report URL in the PR description.

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

Copilot CLI picks the tool from the request — there are no GitHub Copilot CLI-specific commands to learn.

A workflow that sticks

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

Token shape

  • Lives in ~/.copilot/mcp-config.json, a user-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 → and Scoped tokens for AI agents →.

Try it

Add the entry, generate a token, restart GitHub Copilot CLI, 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