Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Manage Meta apps: creation, configuration, webhooks, permissions, compliance, and App Review.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.facebook.com/devtools在终端中运行这条命令
claude mcp add --transport http devtools https://mcp.facebook.com/devtools粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"devtools": {
"url": "https://mcp.facebook.com/devtools"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"devtools": {
"type": "http",
"url": "https://mcp.facebook.com/devtools"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.facebook.com/devtools菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 facebook 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于25天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Dechonet MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Meta Agentic Tools is Meta's marketplace of agent plugins and skills for developers building apps and integrations on the Meta Social Technologies Developer Platform (developers.facebook.com), also known as Meta for Developers: Social Technologies. Manage the Meta apps you build there: settings, webhooks, compliance, app review, and API health, via the Meta Social Technologies MCP.
[!NOTE]
Meta Social Technologies MCP was formerly known as Meta Developer Tools MCP. The server endpoint, the
devtoolsplugin id, and thedevtools_tool name prefix are unchanged, so existing installs and client configurations keep working.
This repo is structured as a multi-plugin marketplace: each product group ships as a self-contained plugin under plugins/, so it can host additional developer plugins alongside the first one, the Meta Social Technologies Developer plugin (devtools). The skills follow the open Agent Skills standard (SKILL.md), so the same skills work in Claude Code, Cursor, and Codex.
All skills call the remote Meta Social Technologies MCP server (
https://mcp.facebook.com/devtools). There is no standalone CLI — the skills drive the MCP for all their work, so connect it after install.
whatsapp-business-integrationalso needs the WhatsApp Business Tools MCP (https://mcp.facebook.com/whatsapp_business_tools). The plugin does not bundle it: add it to your agent's MCP config as shown under Install via Vercel.
claude plugin marketplace add facebook/agentic-tools
claude plugin install devtools@facebook
Then connect the MCP server (its config is bundled with the plugin):
/mcp → connect to devtools → authenticate
Install the devtools plugin from the Cursor marketplace, then authenticate the MCP server:
devtools plugin (published from this repo). The plugin bundles the skills and the Meta Social Technologies MCP config.devtools): Settings → MCP, then complete the OAuth flow.To try it before it's published, copy or symlink plugins/devtools to ~/.cursor/plugins/local/devtools, then run Developer: Reload Window.
Install the skills with the built-in installer, pointing it at this repo:
$skill-installer
Then add the Meta Social Technologies MCP server to ~/.codex/config.toml:
[mcp_servers.devtools]
url = "https://mcp.facebook.com/devtools"
[mcp_servers.whatsapp_business_tools] url = "https://mcp.facebook.com/whatsapp_business_tools"
Codex will run its OAuth flow on first use. Restart Codex after editing the config.
The skills are also listed on Vercel's skills directory, skills.sh, and install with the skills CLI into any agent it supports:
# A single skill
npx skills add facebook/agentic-tools --skill
npx skills add facebook/agentic-tools --skill '*'
[!WARNING]
This installs the skill text only. It does NOT install or authenticate the MCP server — you must add it separately, or the skills cannot run.
Add the Meta Social Technologies MCP server to your agent's MCP config. For whatsapp-business-integration, also add the WhatsApp Business Tools MCP server:
{
"mcpServers": { "devtools": { "type": "streamable-http", "url": "https://mcp.facebook.com/devtools" }, "whatsapp_business_tools": { "type": "streamable-http", "url": "https://mcp.facebook.com/whatsapp_business_tools" } } }
Then complete the OAuth flow for each server in your own agent (for example /mcp in Claude Code), and restart or reload the agent if it does not pick up the new server.
The skills live under plugins/devtools/skills/ rather than a top-level skills/ folder. If npx skills add facebook/agentic-tools -l reports no skills, name one with --skill or pass --full-depth.
| Skill | Description |
|---|---|
/app-health-check | Full app audit — settings, security, compliance, and app review in one report |
/webhook-setup | End-to-end webhook subscription wizard with test verification |
/app-review-prep | App Review readiness check — requirements, privileges, and submission history |
/debug-webhooks | Troubleshoot webhook delivery issues — inspect, test, and fix subscriptions |
/compliance-check | Compliance audit — violations, required actions, and remediation guidance |
/api-health | API health monitoring — rate limits, call volume, and deprecation warnings |
/api-integration | Start a new API integration — fetches setup guides, auth, permissions, and code examples |
/search-docs | Search Meta developer documentation for API guides and references |
/debug-access-token | Diagnose an access token issue (expired, wrong scopes, wrong app, invalid) without the token ever entering the agent context |
/whatsapp-business-integration | Set up WhatsApp Business messaging end to end, from the app to the first sent message |
agentic-tools/
├── server.json # Public MCP registry listing (registry.modelcontextprotocol.io) ├── .github/ │ └── workflows/ │ └── publish-mcp-registry.yml # Publishes server.json to the registry via GitHub OIDC ├── .claude-plugin/ │ └── marketplace.json # Claude Code / Codex marketplace manifest ├── .cursor-plugin/ │ └── marketplace.json # Cursor marketplace manifest (lists plugins by source) ├── .cursor/ │ └── mcp.json # Meta Social Technologies MCP config for manual Cursor setup └── plugins/ └── devtools/ # The Meta Social Technologies Developer plugin ├── .claude-plugin/ │ └── plugin.json # Claude Code plugin manifest ├── .cursor-plugin/ │ └── plugin.json # Cursor plugin manifest ├── .codex-plugin/ │ └── plugin.json # Codex plugin manifest ├── .mcp.json # MCP config for Claude Code / Codex (auto-bundled) ├── mcp.json # MCP config for Cursor (auto-discovered) ├── skills/ # Skill definitions (SKILL.md per workflow) │ ├── app-health-check/ │ ├── webhook-setup/ │ ├── app-review-prep/ │ ├── debug-webhooks/ │ ├── compliance-check/ │ ├── api-health/ │ ├── api-integration/ │ ├── search-docs/ │ ├── debug-access-token/ │ └── whatsapp-business-integration/ └── hooks/ ├── session-init.sh # Session-start hook └── session-context.json # Context injected at session start
The Meta Social Technologies MCP is a remote server — it is not bundled as a process; users authenticate it in their agent.
MIT