Server data from the Official MCP Registry
Plan and send approved engagement on social platforms.
About
Plan and send approved engagement on social platforms.
Security Report
agentic-engage is an engagement draft queue with approval gates, guards, and a generic HTTP webhook adapter; it holds no hardcoded credentials and needs no auth because the caller's endpoint handles delivery. Findings are limited to low-severity observations: the MCP server does not verify account ownership, the 'send' path returns local receipts without real publication, and the MCP tool surface lists 'execute_engagement' which can trigger outbound HTTP to a caller-configured endpoint, but the server source for mcp.ts and index.ts was not provided for full review. Permissions (network_http, process_spawn for CLI) are proportionate to a dispatch/queue tool. Supply chain analysis found 8 known vulnerabilities in dependencies (2 critical, 4 high severity). Package verification found 1 issue.
7 files analyzed · 13 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-pooriaarab-agentic-engage": {
"args": [
"-y",
"agentic-engage"
],
"command": "npx"
}
}
}Documentation
View on GitHubFrom the project's GitHub README.
agentic-engage
agentic-engage is an open-source engagement queue for Node.js developers and agents, with approval steps, local receipts, and a generic HTTP adapter.
Install
npm install agentic-engage
Requires Node.js 18 or later. Includes TypeScript declarations and two runtime dependencies.
Preview your first action
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.
Features and coverage
- Drafts: Generate fixed template text with an AI-assistance disclosure.
- Review: Approve or deny actions; execution requires approved status.
- Queue: Deduplicate target IDs and keep an in-memory audit log.
- HTTP adapter: POST target and text to an endpoint you supply.
- Guards: Optional dispatch caps, UTC quiet hours, and text blocklists.
| 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.
Runtime surfaces
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.
Limits and status
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.
Links and license
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Fetch
Freeby Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.