Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Link building outreach from your agent: review drafts, send the batch, answer publisher replies.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http mentionagent https://mentionagent.ai/mcp --header 'Authorization: your-value'运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"mentionagent": {
"url": "https://mentionagent.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"mentionagent": {
"type": "http",
"url": "https://mentionagent.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 mentionagent.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:Authorization
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Apify MCP Server
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A Claude Code plugin (and a standalone Agent Skill) that runs MentionAgent link building outreach from your agent: review the drafts it wrote, send the batch, answer the publishers who replied, and close placements, without opening the dashboard.
It wraps the MentionAgent MCP server (https://mentionagent.ai/mcp, 38 tools) with a skill that knows the daily loop, which two tools send real email, which two spend credits, and where to stop and ask you.
Works in Claude Code, Cursor, Windsurf, or any MCP client that can set a request header.
claude plugin marketplace add BuildsbyMatt/mentionagent-claude-skill
claude plugin install mentionagent@mentionagent-claude-skill
Then sign in: run /mcp in Claude Code, pick mentionagent and choose Authenticate. A browser window opens on the MentionAgent consent page, you click Allow, and there is no key to paste or store. The connection is listed and revoked in the dashboard under Settings, Agent access.
Prefer an API key (a headless box, CI)? Add the server by hand with a bearer header instead, as under "Install the skill on its own" below. Keys are created under Settings, Agent access and are shown once.
Cursor reads Agent Skills from .cursor/skills/ (project) or ~/.cursor/skills/ (global), and also from .claude/skills/ for compatibility. Copy the skill folder in, then add the server to .cursor/mcp.json:
mkdir -p .cursor/skills
cp -r skills/link-building-outreach .cursor/skills/
{
"mcpServers": { "mentionagent": { "url": "https://mentionagent.ai/mcp", "headers": { "Authorization": "Bearer ma_live_..." } } } }
Type /link-building-outreach in the Agent chat to invoke it. Full walkthrough: https://mentionagent.ai/cursor-seo-skill/
OpenCode reads Agent Skills from .opencode/skills/ (project) or ~/.config/opencode/skills/ (global), and also from .claude/skills/ and .agents/skills/, so a copy installed for Claude Code or Cursor is already visible. Copy the folder in, then add the server as a remote MCP entry in opencode.json and sign in with OAuth (a browser window opens on the MentionAgent consent page):
mkdir -p .opencode/skills
cp -r skills/link-building-outreach .opencode/skills/
{
"$schema": "https://opencode.ai/config.json", "mcp": { "mentionagent": { "type": "remote", "url": "https://mentionagent.ai/mcp", "enabled": true } }, "permission": { "mentionagent_approve_batch": "ask", "mentionagent_send_reply": "ask", "mentionagent_redirect_thread": "ask" } }
opencode mcp auth mentionagent opencode mcp list
The permission rules matter: OpenCode defaults to allow and MCP tools are registered as mentionagent_ , so without them the two tools that send email, and redirect_thread, which opens a thread to an address taken from an email, run without a prompt. Never start OpenCode with --auto in a project that has this server enabled. To use an API key instead of OAuth, set "oauth": false on the server and add "headers": { "Authorization": "Bearer ma_live_..." } with your key. There is no slash command: ask the agent what is waiting on MentionAgent and it loads the skill through its skill tool. Full walkthrough: https://mentionagent.ai/opencode-seo-skill/
OpenClaw reads Agent Skills from /skills/ and ~/.agents/skills/ (the SKILL.md can sit up to six folders deep). Install the folder, register the server, sign in with OAuth (a browser window opens on the MentionAgent consent page), then probe:
openclaw skills install ./skills/link-building-outreach
openclaw mcp add mentionagent \ --url https://mentionagent.ai/mcp \ --transport streamable-http \ --auth oauth --no-probe openclaw mcp login mentionagent openclaw mcp probe mentionagent
To use an API key instead of OAuth, drop --auth oauth and pass --header "Authorization=Bearer ma_live_..." (the flag takes KEY=VALUE; a colon is rejected). openclaw mcp doctor will then flag the literal token, which is the reason to prefer OAuth on a shared Gateway. The skill answers to /link-building-outreach in any connected channel. Full walkthrough: https://mentionagent.ai/openclaw-seo-skill/
Copy skills/link-building-outreach/ into ~/.claude/skills/ (personal) or .claude/skills/ in a project, then connect the MCP server yourself:
claude mcp add --transport http mentionagent https://mentionagent.ai/mcp \
--header "Authorization: Bearer ma_live_..."
Or, in any client that takes a JSON config:
{
"mcpServers": { "mentionagent": { "type": "http", "url": "https://mentionagent.ai/mcp", "headers": { "Authorization": "Bearer ma_live_..." } } } }
Ask your agent: *"Connect to MentionAgent and show me what is waiting."* It calls get_status, lists your sites, and tells you what it can and cannot do on your behalf.
The 38 published tools and nothing else. It cannot see mailbox credentials, billing, domain transfer or account deletion; those stay behind a login. Two tools send email (approve_batch, send_reply) and both are written to be shown to you first. send_reply has no recipient field: the address comes from the thread. The one tool that takes an address is redirect_thread. It sends nothing itself, but it opens a thread to that address, and send_reply on the new thread writes to it. That address usually comes from an inbound email, so the skill shows it to you, with the sentence it came from, and waits for you to confirm before redirecting. set_run_settings with autoSend: true lets future batches go out with no review; the skill only sets it when you ask for it.
Full tool reference and limits: https://mentionagent.ai/mcp/
.claude-plugin/plugin.json plugin manifest
.mcp.json the MentionAgent MCP server, OAuth sign-in skills/link-building-outreach/ the skill (SKILL.md)
The canonical copy of this repo lives in the MentionAgent monorepo under claude-skill/ and is published here on each change.
MIT licensed.