CommentKeyword

com.commentkeyword由 commentkeyword.com 发布v0.2.0更新于 Oct 29, 2026

Create and manage Instagram comment-to-DM keyword automations in CommentKeyword.

已验证STDIO仅桌面沟通与协作商业与电商

概览

AI 生成的概览

让 AI 助手通过 Meta 官方 Instagram API 在 CommentKeyword 账户中创建、修改、暂停和删除 Instagram 评论转私信关键词自动化。

可以做什么
  • 创建评论转私信自动化:关键词、私信与公开回复文案变体、链接追踪,目标可选下一条帖子、全部帖子或指定帖子
  • 修改已有自动化:更换文案、为下次发布重新启用,或将其暂停
  • 列出并查看自动化,检查关键词冲突以及下一条帖子是否已被捕获
  • 删除自动化,若已挂载 AI 智能体则会先请求确认
  • 列出仪表盘中已配置的 AI 智能体,以便挂载到关键词上继续对话
适用场景
适合运营 Instagram 评论转私信活动、希望在与助手的对话中创建、调整或暂停自动化的人,包括在 Reel 仍在剪辑时就为下一条发布做好准备。不适合发布帖子、查看分析数据或管理收件箱。
运行要求
本地 stdio 服务器,通过 npx 运行,需要 Node 18 或更高版本。需要 CommentKeyword 账户并已连接 Instagram 专业(商业或创作者)账户,以及在 COMMENTKEYWORD_API_TOKEN 环境变量中提供的 API 令牌,需具备 keywords:read、keywords:write 和 agents:read 权限。需要访问 CommentKeyword API 的网络;可用 COMMENTKEYWORD_API_URL 覆盖基础地址。
安装前请注意
该令牌是仅限单个工作区的个人凭据,会以 Bearer 头发送给 CommentKeyword API;请妥善保管,泄露后立即撤销。创建或启用自动化会让服务向评论者发送真实的 Instagram 私信,操作前请确认关键词、文案和目标。若令牌含 keywords:delete 权限则可删除自动化。AI 智能体及更高额度需要付费方案。

安装

在 SourceWeft 中

  1. 打开 控制台中的 CommentKeyword,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Instagram MCP Server (Comment-to-DM)

[Instagram MCP Server: comment-to-DM automations from Claude, on Meta's official Instagram API]

An open-source Instagram MCP server that lets Claude, Cursor, Codex and other AI agents set up Instagram comment-to-DM automations ("Comment GUIDE and I'll DM you the link") through Meta's official Instagram API. If you were looking for a ManyChat MCP to build comment automations from Claude, this is the alternative that does it: ManyChat's API can't create keyword or comment triggers, so no ManyChat MCP server can either.

Made by CommentKeyword. MIT-licensed. Registry name com.commentkeyword/mcp.

What it doesCreates, re-targets, pauses and deletes Instagram comment-to-DM keyword automations: keyword, public reply, DM, link tracking, optional AI follow-up
How it reaches InstagramMeta's official Instagram API (professional accounts). No password, no session cookies, no scraping
ClientsClaude Code, Claude Desktop, Cursor, Windsurf, Codex and any MCP client that runs a local stdio server
RunsLocally with npx (Node 18+), no dependencies, no build step. A remote server for claude.ai and ChatGPT is planned
Also in this repoAn Agent Skill that plans the "comment X" CTA of a Reel, a Claude Code plugin, a Remotion comment-to-DM CTA for the end of a Reel, an n8n template and a video-toolkit add-on
PriceThe MCP server and the REST API are included on every CommentKeyword plan, Free too (300 automated DMs a month, 3 active keywords)

What it looks like

You:    Edit this into a Reel. CTA: comment GUIDE to get the free checklist.Claude: …edits the video, adds a "Comment GUIDE 👇" overlay inside the safe zone, writes the caption…        Ready to arm the DM:          Keyword: GUIDE (whole word) · Posts: your next post or reel          DM: "Here's the checklist, {{namefirst}} 👉 https://…"          Public reply: "Sent! Check your DMs 📩"        Create it?You:    YesClaude: Done. GUIDE is waiting for your next post. Publish the Reel, then comment GUIDE from        another account to test it.

The next_post target means you don't need the post's ID: the automation attaches itself to the next post or Reel the account publishes, so you can set it up while the video is still in the edit.

More prompts that work:

  • "Anyone who comments PLAN on my next Reel should get https://example.com/plan by DM. Add a public reply."
  • "Re-arm GUIDE for my next upload."
  • "Which of my keywords are waiting for a post? Pause the ones from last month."
  • "Attach my sales agent to the WEBINAR keyword so it answers follow-up questions."

Instagram MCP server vs ManyChat MCP

People often search for a ManyChat MCP when what they want is to tell Claude "set up comment-to-DM for my next Reel". As of October 2026:

JobThird-party ManyChat MCP serversThis server
Find a contact, tag them, set a fieldYesNo (not a CRM)
Send a message or start a flow you already builtYesNo
Create a keyword / comment-trigger automationNo: ManyChat's API has no endpoint for itYes
Point an automation at your next post or ReelNoYes (next_post)
Edit the DM textNo (it lives in ManyChat's flow editor)Yes, up to 10 variants
Official Instagram APIThrough ManyChatYes
Free plan with API accessNo (ManyChat's API is on paid plans)Yes

ManyChat is still the better tool if you need WhatsApp, Messenger, TikTok or email in one place, or large multi-branch visual flows. Details: ManyChat MCP: what exists and ManyChat alternative for comment-to-DM.

Instagram MCP servers: how this one differs

Meta has no official MCP server for organic Instagram (its official MCP covers ads), so every Instagram MCP server is third-party. Many log in with your password or a session cookie, or scrape public pages. This one only talks to the CommentKeyword API, which uses Meta's official Instagram login and permissions, and it does one job well: comment-to-DM. It doesn't publish posts, read analytics or read your inbox; pair it with a scheduler or an analytics connector for those. Comparison: Instagram MCP servers compared.

Before you start

  1. Create a CommentKeyword account at https://commentkeyword.com. API access is included on every plan, including Free.
  2. Connect an Instagram professional account (Business or Creator).
  3. Create an API token under Settings → API (https://commentkeyword.com/settings?tab=api). Give it keywords:read, keywords:write and agents:read. Add keywords:delete only if you want the agent to be able to delete automations.

Install

Claude Code (skill and MCP server)

/plugin marketplace add commentkeyword/instagram-mcp-server/plugin install commentkeyword@commentkeyword

Claude Code asks for your API token when the plugin is enabled. It stores the token in your system keychain.

Claude Code (MCP server only)

bash
claude mcp add --transport stdio --env COMMENTKEYWORD_API_TOKEN=YOUR_TOKEN commentkeyword -- npx -y github:commentkeyword/instagram-mcp-server#v0.2.0

Claude Desktop, Cursor, Windsurf and other MCP clients

Add the server to the client's MCP config. For Claude Desktop that file is claude_desktop_config.json (Settings → Developer → Edit Config).

json
{  "mcpServers": {    "commentkeyword": {      "command": "npx",      "args": ["-y", "github:commentkeyword/instagram-mcp-server#v0.2.0"],      "env": { "COMMENTKEYWORD_API_TOKEN": "YOUR_TOKEN" }    }  }}

Skill only (Claude.ai, Claude Desktop, other agents that read SKILL.md)

With the skills CLI (Claude Code, Cursor, Codex and other agents):

bash
npx skills add commentkeyword/instagram-mcp-server

Or by hand:

  1. Download skills/comment-to-dm-cta as a folder and zip it.
  2. In Claude, upload the zip under Customize → Skills → Upload a skill.

Without the MCP server, the skill still plans the CTA and the DM. It can also call the REST API directly where the agent has network access (see references/api.md).

Add-ons for video toolkits

ToolkitAdd-on
Remotionintegrations/remotion: an animated "comment the keyword, get the DM" box for the end of a Reel. It shows your real public reply, DM, handle and profile picture, read from your automation
claude-code-video-toolkitintegrations/claude-code-video-toolkit: a /comment-dm command that reads the CTA from the project and arms the DM before you publish

n8n

integrations/n8n has an importable n8n workflow that creates the comment-to-DM automation for your next post through the REST API, with Header Auth and no code.

MCP tools

ToolWhat it does
create_keywordCreate an automation. target is next_post, all_posts or specific_posts. Also takes up to 10 DM variants, up to 10 public reply variants, link tracking, and an existing AI agent to attach (aiAgentId, paid plans).
update_keywordChange any field. Re-arm it for the next upload with target: "next_post", or pause it with isActive: false.
list_keywords / get_keywordCheck for conflicts and see whether the next post was caught (nextPostStatus).
delete_keywordDelete an automation. Asks for confirmation when an AI agent is attached.
list_agentsList the AI agents already set up in your dashboard, so one can be attached to a keyword to continue the conversation after the first DM. Agents are created and edited in the dashboard, not through the API.
Environment variable
COMMENTKEYWORD_API_TOKENRequired. Your personal access token.
COMMENTKEYWORD_API_URLOptional. Defaults to https://commentkeyword.com/api.

Network and data

  • One destination. The MCP server and the skill's curl examples only call the CommentKeyword API, at https://commentkeyword.com/api (or COMMENTKEYWORD_API_URL if you set it). No telemetry, no other hosts.
  • What gets sent: your API token (as a Bearer header) and the automation you confirm: keyword, DM and reply text, target posts and options.
  • What comes back: your keyword automations and the names of your AI agents.
  • Nothing on disk. The server stores nothing locally.
  • Privacy policy: https://commentkeyword.com/privacy

Safety

  • Every automation messages real people. The skill and the tool descriptions tell the agent to confirm the keyword, the DM and the target with you before creating or activating anything.
  • Each token works for one workspace and can be revoked at any time in Settings → API.
  • Use the narrowest permissions you need.

Development

bash
npm test   # end-to-end tests: spawns the server over stdio against a mock API

The MCP server has no dependencies and no build step. It is two readable files in server/: core.mjs holds the tools, the validation and the JSON-RPC handling; commentkeyword-mcp.mjs is the stdio entry point. It needs Node 18 or newer.

FAQ

Is there an official Instagram MCP server? No. Meta's official MCP server is for ads. Every MCP server for posts, comments and DMs is third-party, so check whether it uses the official API. This one does.

Does ManyChat have an MCP server? Not an official one, as of October 2026. Third-party wrappers can tag contacts and trigger existing flows, but can't create comment automations, because ManyChat's API doesn't allow it.

Can Claude send Instagram DMs with this? It sets up automations; CommentKeyword then sends the DMs within Instagram's rules: one private reply per comment within 7 days, and more messages within 24 hours after the person writes back.

Is it allowed by Meta? It uses Meta's official Instagram API with permissions you approve, and messages only people who commented your keyword. See Is Instagram DM automation allowed?.

Does it work with ChatGPT or claude.ai in the browser? Not yet: those need a remote MCP server, which is planned. Codex, Claude Code, Claude Desktop, Cursor and Windsurf work today.

What does it cost? The server is free and open source. The CommentKeyword service has a Free plan that includes the API; paid plans add DMs, keywords and AI agents. Pricing.

Links

License

MIT. Maintained by CommentKeyword. Issues and PRs welcome.

来源:README.md,提交 556fba3

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.2.0最新Oct 29, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分