How do I add a remote MCP server to Zed?

Add an entry under `context_servers` in settings.json with `url` and optional `headers`, or use Settings → AI → MCP Servers → Add Remote Server.

Why does Zed ask me to sign in to an MCP server?

Zed starts OAuth when a remote context server has no `Authorization` header. Comma uses a `comma_sk_` token — add it as `Authorization: Bearer …` and the prompt goes away.

Do I need to run anything locally for Comma's MCP server?

No. Comma's MCP server is hosted at https://commareports.com/api/mcp over Streamable HTTP. The config entry and a `comma_sk_` token are the whole setup — unless you use the `mcp-remote` bridge, which runs via `npx`.

Is Comma free to use from Zed?

Yes. Publishing reports, inviting commenters and keeping revisions are free. Routines — scheduled runs Comma hosts — are the paid part.

Use Comma with Zed

Zed calls MCP servers "context servers". Comma is a remote one, and because you set the Authorization header yourself, Zed connects straight away instead of starting an OAuth flow.

Add Comma to Zed

Open the settings file (zed: open settings) and add to context_servers, or go to Settings → AI → MCP Servers → Add Server → Add Remote Server.

{
  "context_servers": {
    "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.

Zed gotchas

Set the header, skip OAuth. Zed only prompts for OAuth on a remote server with no Authorization header — with the header present it uses your scoped token directly.
If the server fails to start, check the header value includes the Bearer prefix — a bare token is rejected.
Add a rule in Zed's Rules Library to publish documents to Comma, so you don't have to ask each thread.

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`

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

A workflow that sticks

Ask Zed'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.
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.
Next session, ask Zed'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 Zed can be revised tomorrow from Claude Code or Cursor, and the link people bookmarked keeps working.

Token shape

Lives in Zed's user settings.json. If you sync settings via dotfiles, move the token out first.
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 Zed, 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 →