MCP servers that can list comments
4 verified servers expose a tool that can list comments on an object
Comments are where the discussion around a thing lives, and an agent that needs to catch up on a record, a design, or a page reads them. Listing comments returns that thread, so the model can summarize the conversation or answer from what people actually said.
These verified servers let an agent list the comments on an object.
Airtable
Adam Jones (domdomegg)
Maintained Airtable MCP server: let an agent inspect base schemas, then read, search, and write records, tables, fields, and comments.
list_comments
Airtable's list_comments returns the comments on a record, with pagination, the thread an agent reads before replying on a row.
Attio
Attio
Attio's official remote MCP server connects AI agents to your CRM over OAuth to search, read, create, and update records, lists, notes, and more.
list-comments
Attio's list-comments returns comments with their top-level and inline replies, the full discussion on a CRM object.
Canva
Canva
Canva's official remote MCP server lets agents generate, edit, search, and export designs over OAuth.
list-comments
On Canva, list-comments returns the comments on a design, so an agent can catch up on feedback before acting on it.
Notion
Notion
Notion's hosted MCP server lets agents search, read, and write across your workspace over OAuth.
notion-get-comments
notion-get-comments lists all comments and discussions on a Notion page, the read behind summarizing or answering a thread.
What to know
Reading comments is the counterpart to adding one: before an agent replies or summarizes, it pulls the existing thread. What carries a comment differs by server, an Airtable record, an Attio object, a Canva design, a Notion page, but the read is the same: return the comments, often with their replies, so the agent sees the full discussion. From there it can answer a question, draft a reply, or flag what needs a human.
A comment thread grows as people add to it, so re-reading catches what is new. What an agent benefits from holding is its own place in the thread: which comments it already processed, so a follow-up reads only what arrived since rather than re-summarizing the whole conversation.
Questions
- How does this pair with adding a comment?
- Listing reads the thread; adding writes to it. An agent usually lists the existing comments first, to catch up or avoid repeating a point, then adds its own. The two are the read and write halves of a discussion.
- Does it include replies?
- On some servers, yes. Attio returns top-level and inline replies, and Notion lists comments and discussions together. Others return a flat list. If threaded replies matter, check whether the server returns them or only the top-level comments.