MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
제작자가 쓴 설명(영어 원문)
Create and manage Instagram comment-to-DM keyword automations in CommentKeyword.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
COMMENTKEYWORD_API_TOKEN, COMMENTKEYWORD_API_URL비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
링크는 제작자의 파일로 바로 연결돼요. 우리가 보관하거나 다시 패키징하지 않아요. 파일을 열면 Claude Desktop이 설치해요.
터미널에서 이 명령어를 실행하세요
실행하기 전에 빈 값을 채워 주세요.
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
COMMENTKEYWORD_API_URL env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 commentkeyword.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: COMMENTKEYWORD_API_TOKEN
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.2.0)은 10일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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 does | Creates, re-targets, pauses and deletes Instagram comment-to-DM keyword automations: keyword, public reply, DM, link tracking, optional AI follow-up |
| How it reaches Instagram | Meta's official Instagram API (professional accounts). No password, no session cookies, no scraping |
| Clients | Claude Code, Claude Desktop, Cursor, Windsurf, Codex and any MCP client that runs a local stdio server |
| Runs | Locally with npx (Node 18+), no dependencies, no build step. A remote server for claude.ai and ChatGPT is planned |
| Also in this repo | An 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 |
| Price | The MCP server and the REST API are included on every CommentKeyword plan, Free too (300 automated DMs a month, 3 active keywords) |
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: Yes Claude: 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:
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:
| Job | Third-party ManyChat MCP servers | This server |
|---|---|---|
| Find a contact, tag them, set a field | Yes | No (not a CRM) |
| Send a message or start a flow you already built | Yes | No |
| Create a keyword / comment-trigger automation | No: ManyChat's API has no endpoint for it | Yes |
| Point an automation at your next post or Reel | No | Yes (next_post) |
| Edit the DM text | No (it lives in ManyChat's flow editor) | Yes, up to 10 variants |
| Official Instagram API | Through ManyChat | Yes |
| Free plan with API access | No (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.
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.
keywords:read, keywords:write and agents:read. Add keywords:delete only if you want the agent to be able to delete automations./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 mcp add --transport stdio --env COMMENTKEYWORD_API_TOKEN=YOUR_TOKEN commentkeyword -- npx -y github:commentkeyword/instagram-mcp-server#v0.2.0
Add the server to the client's MCP config. For Claude Desktop that file is claude_desktop_config.json (Settings → Developer → Edit Config).
{
"mcpServers": { "commentkeyword": { "command": "npx", "args": ["-y", "github:commentkeyword/instagram-mcp-server#v0.2.0"], "env": { "COMMENTKEYWORD_API_TOKEN": "YOUR_TOKEN" } } } }
SKILL.md)With the skills CLI (Claude Code, Cursor, Codex and other agents):
npx skills add commentkeyword/instagram-mcp-server
Or by hand:
skills/comment-to-dm-cta as a folder and zip it.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).
| Toolkit | Add-on |
|---|---|
| Remotion | integrations/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-toolkit | integrations/claude-code-video-toolkit: a /comment-dm command that reads the CTA from the project and arms the DM before you publish |
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.
| Tool | What it does |
|---|---|
create_keyword | Create 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_keyword | Change any field. Re-arm it for the next upload with target: "next_post", or pause it with isActive: false. |
list_keywords / get_keyword | Check for conflicts and see whether the next post was caught (nextPostStatus). |
delete_keyword | Delete an automation. Asks for confirmation when an AI agent is attached. |
list_agents | List 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_TOKEN | Required. Your personal access token. |
COMMENTKEYWORD_API_URL | Optional. Defaults to https://commentkeyword.com/api. |
https://commentkeyword.com/api (or COMMENTKEYWORD_API_URL if you set it). No telemetry, no other hosts.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.
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.
MIT. Maintained by CommentKeyword. Issues and PRs welcome.