Comment.io MCP Server

by comment-hq Your server? Claim it

answering

Comment.io is answering right now. Last checked 8 min ago.

Read, edit and improve shared documents and knowledge with people and agents.

Uptime history 4 days of history · worst day 97%

4 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

424 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Comment.io does not always answer

Over the last week it answered 98.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add comment --transport http https://comment.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "comment": {
      "url": "https://comment.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.comment]
url = "https://comment.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "comment": {
      "url": "https://comment.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "comment": {
      "url": "https://comment.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://comment.io/mcp	streamable-http	sign-in	398 ms	8 min ago

Alternatives to Comment.io

same job, measured the same way

Google Docs MCP

by mmedum

Google Docs as MCP tools: read, edit, suggest and comment on documents.

local only

Google Docs MCP

by a1-x-tech

MCP server for the Google Docs API: read and edit documents, styles, tables, images, comments.

54 installs/wk local only

ClearMakes Agents

by clearmakes

Search one ClearMakes agent's knowledge: your documents, website pages and Drive files.

answering

MCP Ooxml Ledger

by anselmoo

Edit Office documents and prove no edit went unrecorded

161 installs/wk local only

Postgram

by ivo-toby

Self-hosted memory for AI agents with hybrid search, knowledge graphs, tasks, and document sync.

local only

llmwiki

by atomicstrata

Compile documents into a cited knowledge wiki. Retrieve evidence, query, and review via local MCP.

1 230 installs/wk local only

PasteMD

by jini-tw

Instant markdown sharing. Create, manage, and share documents with password protection.

answering

Pdfco

by mcparmory

Extract data, edit, convert, and parse PDF documents with OCR and AI

239 installs/wk local only

Comment.io — questions

Answers built from our own checks of this server.

Why is there no tool list for Comment.io?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Comment.io working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 424 ms. The bar chart above shows every period we have measured.

How do I connect Comment.io?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Comment.io?

No API key is involved. Comment.io answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Comment.io?

It answers our handshake in 424 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.