Commentify

one.commentifyPublished by commentify.oneOfficial publisherv1.2.0Updated Oct 30, 2026

Your team's design feedback from Figma, Jira and Notion: ask, search, read, reply, mark done.

Overview

AI-generated overview

Commentify brings your team's Figma, Jira and Notion comment threads into an assistant so it can answer, search, reply and close feedback.

What you can do
  • Ask what the team said about a screen, file or ticket, with answers citing the threads
  • Look up feedback on UI files, components or tickets while working on code
  • Draft and post replies in your name after you confirm
  • Mark handled threads done after you confirm the list
When to use it
Useful when design and product feedback lives in Figma, Jira and Notion comment threads and you want an assistant to surface decisions and open questions while coding or reviewing UI work, or to answer and close threads without switching apps.
Requirements
A remote endpoint at app.commentify.one with OAuth sign-in. A Commentify account with at least one of Figma, Jira or Notion connected under Settings. Reading is available on every plan within a daily limit; replying and closing threads need the Pro plan.
Before you install
Replying and marking threads done write to Figma, Jira or Notion in your name, though the README says each action is shown for confirmation first. Your questions, mentioned file paths and ticket keys, and confirmed replies are sent to app.commentify.one. Reading is capped by a daily limit, and write actions require a paid plan.

Installation

In SourceWeft

  1. Open Commentify in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/one.commentify%2Fcommentify/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "commentify": {
      "type": "http",
      "url": "https://app.commentify.one/api/mcp"
    }
  }
}

README

Commentify

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

  1. Sign up at app.commentify.one and connect at least one of Figma, Jira or Notion under Settings → Connect.

  2. Install this plugin. In Claude Code, one line does it:

    /plugin install commentify --marketplace oneSlash-app/commentify-plugin

    On 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 /mcp and sign in when the browser opens.

  3. 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

SkillWhen Claude uses it
design-feedback-digestA question about what the team said, or a digest of open threads
feedback-for-codeWorking on UI files, a component or a ticket that designers commented on
reply-to-feedbackAnswering a thread in your name (Pro)
close-feedback-threadsMarking 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.

Source: README.md at commit 0f96275

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.2.0LatestOct 22, 2026
  2. v1.1.0Oct 18, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts