Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Plan and send approved engagement on social platforms.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agentic-engage": {
"command": "npx",
"args": [
"-y",
"agentic-engage",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add agentic-engage -- npx -y agentic-engage mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentic-engage": {
"command": "npx",
"args": [
"-y",
"agentic-engage",
"mcp"
]
}
}
}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": {
"agentic-engage": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentic-engage",
"mcp"
]
}
}
}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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account pooriaarab, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Intervals MCP
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.
Remote MCP server for intervals.icu run data and analysis
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.
agentic-engage is an open-source engagement queue for Node.js developers and agents, with approval steps, local receipts, and a generic HTTP adapter.
npm install agentic-engage
Requires Node.js 18 or later. Includes TypeScript declarations and two runtime dependencies.
Save this as preview.mjs, then run node preview.mjs. No credentials are needed.
import {
createEngagementQueue, planEngagement, approveEngagement, executeEngagement, getCostReport, } from "agentic-engage";
const queue = createEngagementQueue(); const [draft] = planEngagement( [{ id: "post-1", platform: "webhook", context: "your launch" }], "Helpful brand", queue, ); approveEngagement(draft.id, queue); const preview = await executeEngagement(draft.id, { queue }); console.log(preview.dryRun, preview.action.status); // true approved console.log(getCostReport()); // entries: [], dispatches: 0, units: 0
Success prints true approved and zero dispatch costs. Preview makes no delivery request.
| Target label | Native integration status |
|---|---|
| scaffold; generic HTTP or local receipt only | |
| X (Twitter) | scaffold; generic HTTP or local receipt only |
| scaffold; generic HTTP or local receipt only | |
| YouTube | scaffold; generic HTTP or local receipt only |
| Bluesky | scaffold; generic HTTP or local receipt only |
| Webhook | Generic HTTP adapter implemented; endpoint supplied by caller |
Six target labels share two engagement adapter classes. No native social API is credential-verified. Use new HttpEngagementAdapter("webhook", { endpoint }) in the library's adapters map. Your endpoint handles authentication and platform delivery. No vendor environment variables or .env loader exist.
CLI commands: plan, queue, approve, deny, send, costs, and mcp; also --help and --version. Run npx agentic-engage mcp or npx --package agentic-engage agentic-engage-mcp for Model Context Protocol (MCP). Tools: plan_engagement, get_engagement_queue, approve_engagement, deny_engagement, execute_engagement, and get_cost_report. Worker source exposes GET /health, POST /summarize, and POST /plan; you deploy it yourself.
Queues and costs reset when the process exits. Separate CLI invocations do not share actions. CLI and MCP live execution use local receipts; they cannot configure HTTP adapters. Library execution also defaults to local receipts without an adapter, even with live: true. A sent status therefore does not prove social publication. HTTP receipts use locally generated IDs. HTTP requests default to a 10-second timeout with no retries. Costs count characters, not currency. Drafts use fixed text templates; no language model generates them. Account ownership is not verified. Version 0.1.0 has an API that may change. No managed social delivery service is included.