Commentify MCP server
Commit Oct 18, 2026Aggregates design feedback from Figma, Jira, and Notion to allow AI clients to search, read, reply to, and manage comment threads.
Also known as oneSlash-app/commentify-plugin, commentify-plugin
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.2.0
- Last commit
- Oct 18, 2026
- License
- MIT
What is Commentify MCP?
Commentify aggregates design feedback from Figma, Jira, and Notion to allow AI clients to search, read, reply to, and manage comment threads.
Summary generated from the project's README
About Commentify MCP server
Commentify centralizes design feedback from Figma, Jira, and Notion into a single interface for AI clients. It allows developers and designers to search, read, and manage comment threads directly through Claude. By connecting these disparate platforms, the server enables an AI to provide digests of team discussions or check for open feedback before code changes are implemented.
Users set up the server by signing up at the Commentify website and connecting their preferred tools. Installation is handled via a single command in Claude Code or through the plugin settings in Claude.ai and Cowork. While reading threads is available on all plans within a daily limit, advanced features like replying to feedback or closing threads require a Pro plan. The plugin itself stores no data, sending only necessary context like file paths and ticket keys to the Commentify connector to retrieve relevant discussions.
What you can do with it
- 1Summarize team discussionsAsk the AI to provide a summary of what the team has said regarding a specific page or project.
- 2Verify feedback before codingCheck for existing design decisions or open questions related to a specific UI component before making changes.
- 3Respond to commentsDraft and post replies to feedback threads in your name after reviewing the AI's suggestion.
- 4Resolve feedback threadsMark comment threads as completed once the necessary tasks have been handled.
Written from the project's README. Every use case is checked against a quote from it.
How to install Commentify MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Commentify MCP in Claude Code
$ claude mcp add --transport http commentify-plugin https://app.commentify.one/api/mcpInstall Commentify MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"commentify-plugin": {
"url": "https://app.commentify.one/api/mcp"
}
}
}Install Commentify MCP in VS Code
.vscode/mcp.json
{
"servers": {
"commentify-plugin": {
"type": "http",
"url": "https://app.commentify.one/api/mcp"
}
}
}Install Commentify MCP in VS Code CLI
$ code --add-mcp '{"name":"commentify-plugin","type":"http","url":"https://app.commentify.one/api/mcp"}'Install Commentify MCP in Codex
$ codex mcp add commentify-plugin --url https://app.commentify.one/api/mcpInstall Commentify MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.commentify-plugin] url = "https://app.commentify.one/api/mcp"
Install Commentify MCP in Gemini CLI
$ gemini mcp add -s user --transport http commentify-plugin https://app.commentify.one/api/mcpInstall Commentify MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"commentify-plugin": {
"url": "https://app.commentify.one/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableoneslash-app/commentify-plugin is public and reachablegithub.com/oneslash-app/commentify-plugin ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-22github.com/oneslash-app/commentify-plugin ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubCommentify
Your team's design feedback from Figma, Jira and Notion, in Claude.
Commentify brings the comment threads from your Figma files, Jira issues and Notion pages into one place. This plugin connects Claude to it, and teaches Claude how to use it well.
What it does
- Ask what the team said. "What did the team say about the Inbox page?" "Is there open feedback on PROJ-123?" Claude answers from the threads and cites them.
- Check feedback before changing code. When you work on a screen or a component, Claude looks up the threads about those files and brings the decisions and open questions into the work.
- Reply in your name. Claude drafts a reply, shows it to you, and posts it on Figma, Jira or Notion once you confirm. Pro plan.
- Close threads. Mark threads done in Commentify when they are handled, after you confirm the list. Pro plan.
Setup
-
Sign up at app.commentify.one and connect at least one of Figma, Jira or Notion under Settings → Connect.
-
Install this plugin. In Claude Code, one line does it:
/plugin install commentify --marketplace oneSlash-app/commentify-pluginOn claude.ai and in Cowork, add it from Customize → Plugins, then connect the Commentify connector from the plugin's Connectors tab and sign in. In Claude Code, run
/mcpand sign in when the browser opens. -
Ask Claude about your feedback.
Reading is on every Commentify plan, within a daily limit. Replying and marking threads done need the Pro plan. The full guide is at app.commentify.one/docs/agents.
Data
The plugin sends your questions, the file paths and ticket keys you mention, and the replies you confirm to Commentify at app.commentify.one, over the connector you sign in to. Commentify answers with your own team's comment threads. The plugin stores nothing itself. Commentify's privacy policy is at commentify.one/privacy-policy.
Skills
| Skill | When Claude uses it |
|---|---|
design-feedback-digest |
A question about what the team said, or a digest of open threads |
feedback-for-code |
Working on UI files, a component or a ticket that designers commented on |
reply-to-feedback |
Answering a thread in your name (Pro) |
close-feedback-threads |
Marking handled threads done (Pro) |
MCP registry
The server is listed in the MCP registry as one.commentify/commentify, so any client that reads the registry can find it under the same name. The listing is maintained from Commentify's own repository, not from here.
Commentify MCP questions
How do I add Commentify MCP to Claude Code?
Run claude mcp add --transport http commentify-plugin https://app.commentify.one/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Commentify MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can Claude reply to comments for me?
Yes, Claude can draft a reply and post it to Figma, Jira, or Notion once you confirm it, but this requires a Pro plan.
Is there a limit to how much I can read?
Reading is available on every plan but is subject to a daily limit.
Does the plugin store my data?
No, the plugin itself does not store any data; it sends information to Commentify over a secure connector.
How do I mark feedback as completed?
You can mark threads as done in Commentify after confirming the list, which is a Pro plan feature.