Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Link building outreach from your agent: review drafts, send the batch, answer publisher replies.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http mentionagent https://mentionagent.ai/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mentionagent": {
"url": "https://mentionagent.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mentionagent": {
"type": "http",
"url": "https://mentionagent.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain mentionagent.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, AlphaGrowth
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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.
Free crypto data for AI agents: TVL, fees, funding, investors, yields, token unlocks, DAO treasuries
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.