agentic-campaign
Advanced tools
Social campaign planning, draft approvals, and queue exports for Node.js and TypeScript, with CLI and Model Context Protocol tools.
Package · Quickstart · Runtime surfaces
agentic-campaign is an open-source social campaign planner for developers who need draft calendars, explicit slot approval, and text queue exports. It runs as a TypeScript SDK, command-line interface (CLI), or Model Context Protocol (MCP) server. Campaign planning and approval run locally; this package never publishes social posts.
npm install agentic-campaign
Node.js 18 or later is required. TypeScript declarations are included, with two direct runtime dependencies.
Save this as campaign-demo.mjs. No credentials, environment variables, or .env loader are required.
import { createCampaign, approveSlot, exportQueue } from "agentic-campaign";
const campaign = createCampaign({
brand: "Acme",
goal: "launch a feature",
platforms: ["linkedin", "x"],
weeks: 1,
postsPerWeek: 2,
startDate: "2026-11-01",
});
console.log(campaign.schedule.length);
console.log(exportQueue(campaign).length);
const approved = approveSlot(campaign, "slot-1", { live: true, approved: true });
const queue = exportQueue(approved);
console.log(queue.length, queue[0].brand, queue[0].targets[0]);
node campaign-demo.mjs
Success prints 2, 0, and 1 Acme linkedin.
The approval flags change local state; they do not send a post.
Export text includes an AI-assistance disclosure and needs editorial review.
Brief -> deterministic pillars and daily draft slots
Draft slot + explicit approval -> approved slot
Approved or scheduled slots -> { brand, text, targets } queue
Queue -> a downstream publisher you implement separately
Developers need campaign planning data they can inspect and pass between tools. Buffer and Hootsuite provide social calendars with publishing workflows. agentic-campaign supplies local plan generation and approval-filtered text exports for code and agent sessions.
Scope checked on 2026-10-14 against the official pages linked below.
| Scope | agentic-campaign | Buffer | Hootsuite |
|---|---|---|---|
| Main workflow | Generate local plans and export drafts | Plan, schedule, and publish social posts | Plan, schedule, and publish social posts |
| Calendar representation | In-memory campaign objects | Product content calendar | Product content calendar |
| Publishing in this package | None | No Buffer adapter | No Hootsuite adapter |
| Surface | Status | Behavior |
|---|---|---|
| Campaign brief | ✓ | Brand, goal, platform labels, slot count, and start date |
| Content pillars | ✓ | Three fixed pillars: Educate, Proof, Engage |
| Format labels | ✓ | Four rotating labels: short post, carousel, video, story |
| Slot approval | ✓ | Draft-to-approved transition with two explicit flags |
| Queue export | ✓ | Approved and scheduled slots become text queue items |
| LinkedIn and X (Twitter) | Labels only | Example target strings; no network adapters |
| Other platform names | Labels only | Arbitrary nonempty strings; no support registry |
| Local text router | scaffold | Receipt generation only |
| Generic HTTP text router | ✓ | Posts {text} to your endpoint; separate from campaign export |
| Cloudflare Workers handler | scaffold for campaigns | Health and text summary only; no campaign routes |
There are zero social publishing connectors, two shared text-routing adapters, three fixed pillars, and four format labels. The source and local tests verify planning behavior. Zero external integrations were credential-checked for this rewrite.
{brand, text, targets} queue items through their own pipeline.createCampaign builds draft slots; see the quickstart.approveSlot requires live: true and approved: true.exportQueue keeps approved or scheduled slots and includes draft disclosure text.The Node.js SDK exports createCampaign, approveSlot, exportQueue, and shared text utilities.
| CLI command | Behavior |
|---|---|
campaign create --brand Acme --goal launch --platforms linkedin,x --weeks 1 --posts-per-week 2 | Print a new campaign; accepts --start-date |
campaign list | List campaigns from the current process map |
campaign show --id <id> | Read a campaign from that map |
campaign approve-slot --id <id> --slot slot-1 --live --approve | Approve a draft in that map |
campaign export --id <id> | Export approved or scheduled slots from that map |
costs | Print current process cost units |
mcp | Start the stdio server |
Run commands with npx agentic-campaign. --help and --version print help and version output.
Separate CLI invocations start fresh maps. Use the SDK or a persistent MCP session for the full lifecycle.
All six MCP tools: create_campaign, list_campaigns, show_campaign, approve_campaign_slot, export_campaign_queue, and get_cost_report.
Start them with npx agentic-campaign mcp or npx agentic-campaign-mcp.
The Worker source exposes GET /health and POST /summarize only.
Optional PACK_NAME changes its health response label. You deploy and secure the Worker yourself.
weeks * postsPerWeek sets total slots across all labels, rather than slots per platform.weeks does not bound the schedule to that many weeks.quietHours is accepted but ignored. Slots contain dates, without posting times.The export tool describes its shape as agentic-publish-compatible in source. This package does not call agentic-publish or verify delivery compatibility. No separate public documentation site is configured.
Version 0.1.0 is an early release; APIs can change before 1.0. Report problems through GitHub issues. Public case studies are not published in this repository.
agentic-campaign generates local campaign plans and exports reviewed draft text. It provides SDK, CLI, and MCP interfaces for developers.
agentic-campaign has no social publishing connectors or platform credential verification. Its shared generic HTTP text router is separate from the campaign workflow.
agentic-campaign produces data inside your process. You supply storage, deployment, editorial review, and any publisher.
agentic-campaign generates campaign objects and approval-filtered queues in code. Buffer provides a social planning and publishing product; see its publishing overview.
agentic-campaign exposes a local planning SDK and agent tools. Hootsuite provides a content calendar and publishing workflows; see its publishing overview.
agentic-campaign stores those names as target labels. It makes no social network requests and validates no platform-specific constraints.
agentic-campaign starts a fresh in-memory map for each standalone CLI invocation. Use a shared SDK object or one persistent MCP server session to retain campaigns.
agentic-campaign uses fixed pillar descriptions and hook templates. Its export includes an AI-assistance disclosure, but no model API is called.
agentic-campaign requires both live and approval flags to change a draft slot to approved. That local state change makes the slot eligible for export and sends nothing externally.
Run npm ci, npm run build, npm run typecheck, and npm test from the repository.
MIT. See the license text.
FAQs
Social campaign planning, draft approvals, and queue exports for Node.js and TypeScript, with CLI and Model Context Protocol tools.
The npm package agentic-campaign receives a total of 0 weekly downloads. As such, agentic-campaign popularity was classified as not popular.
We found that agentic-campaign demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Security News
The PHP Foundation says Chainguard broke a security embargo ahead of critical RCE patches, as leaks disrupted the coordinated release.
Security News
PHP releases emergency patches for two critical RCE vulnerabilities as agencies urge organizations to take unpatched sites offline.
Threat Research
/Security News
A supply chain attack compromised LiteLLM 1.107.0 on PyPI and Docker, spreading malware that steals cloud credentials, developer secrets, and AI provider keys.