Agentic Campaign

Name: Agentic Campaign
Author: pooriaarab

作者：pooriaarab版本 0.1.0i★ –i在你的电脑上运行

注册名称io.github.pooriaarab/agentic-campaign

安装

概览

作者提供的说明（英文原文）

Plan a social campaign calendar across brands and platforms.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 营销与社交媒体

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "agentic-campaign": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-campaign",
        "mcp"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add agentic-campaign -- npx -y agentic-campaign mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentic-campaign": {
      "command": "npx",
      "args": [
        "-y",
        "agentic-campaign",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "agentic-campaign": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agentic-campaign",
        "mcp"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 pooriaarab 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“营销与社交媒体”中的其他服务器比较i

星标数多于此分类中其他 2982 个服务器的 0%
发布到注册中心的时间比此分类中其他 2982 个服务器的 57% 更新
基础检查结果等于或优于此分类中其他 2982 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Agentic Campaign 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.0）于23天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

MCP YouTube Transcript

作者：jkawamoto

An MCP server retrieving transcripts of YouTube videos

在你的电脑上运行★ 495MIT10天前更新

安装

Google Analytics MCP

作者：surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

在你的电脑上运行★ 244MIT10天前更新

安装

BibiGPT YouTube Video Summarizer

作者：JimmyLv

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

在云端运行★ 137MIT10天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

agentic-campaign

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.

Install

npm install agentic-campaign

Node.js 18 or later is required. TypeScript declarations are included, with two direct runtime dependencies.

Export your first campaign draft

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.

How it works

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

Why it exists

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.

Compare

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

Coverage

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.

Common use cases

Node.js release teams generate draft slots for LinkedIn and X (Twitter) labels.
TypeScript agencies plan separate campaign objects for client brands.
MCP client developers review and approve slots within one agent session.
Custom publisher developers consume {brand, text, targets} queue items through their own pipeline.

Features

Campaign plans: createCampaign builds draft slots; see the quickstart.
Explicit approvals: approveSlot requires live: true and approved: true.
Queue exports: exportQueue keeps approved or scheduled slots and includes draft disclosure text.
Agent sessions: MCP tools retain campaigns in the server's in-memory map.
Shared utilities: Text summaries, generic dispatch, guards, logging, and in-memory cost reports are SDK exports.

Runtime surfaces

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`	Read a campaign from that map
`campaign approve-slot --id --slot slot-1 --live --approve`	Approve a draft in that map
`campaign export --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.

Delivery and behavior limits

weeks * postsPerWeek sets total slots across all labels, rather than slots per platform.
Slots advance one calendar day each. weeks does not bound the schedule to that many weeks.
Brief quietHours is accepted but ignored. Slots contain dates, without posting times.
The daily cap is SDK-only input; the generator still advances a day after each slot.
Pillars, hooks, and formats use fixed code templates. No language model generates campaign text.
Format labels do not create carousel images, videos, stories, or attachments.
Campaign IDs use normalized brand and start date. Same-brand, same-date plans can overwrite a session map entry.
CLI and MCP storage is in memory. There is no file store, database, or restart recovery.
Only draft-to-approved transitions have an exported helper. Scheduling and completion need application code.
Queue items omit dates, slot IDs, and media. Downstream code must preserve scheduling metadata separately.
There is no automatic delivery, retry, deduplication, platform authentication, or engagement analytics.
Cost reports track generic text dispatch units. Campaign planning and approvals record no costs.

Integration guides

Node.js campaign approval and export example
CLI and MCP campaign lifecycle reference
Export and storage constraints

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.

Status

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.

FAQ

What is agentic-campaign?

agentic-campaign generates local campaign plans and exports reviewed draft text. It provides SDK, CLI, and MCP interfaces for developers.

Which integrations are verified?

agentic-campaign has no social publishing connectors or platform credential verification. Its shared generic HTTP text router is separate from the campaign workflow.

Does agentic-campaign provide a managed publishing service?

agentic-campaign produces data inside your process. You supply storage, deployment, editorial review, and any publisher.

How is agentic-campaign different from Buffer?

agentic-campaign generates campaign objects and approval-filtered queues in code. Buffer provides a social planning and publishing product; see its publishing overview.

How is agentic-campaign different from Hootsuite?

agentic-campaign exposes a local planning SDK and agent tools. Hootsuite provides a content calendar and publishing workflows; see its publishing overview.

Does agentic-campaign publish to LinkedIn or X (Twitter)?

agentic-campaign stores those names as target labels. It makes no social network requests and validates no platform-specific constraints.

Why does agentic-campaign list show no campaigns after create?

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.

Does agentic-campaign generate copy with a language model?

agentic-campaign uses fixed pillar descriptions and hook templates. Its export includes an AI-assistance disclosure, but no model API is called.

What does live approval do?

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.

Contributing

Run npm ci, npm run build, npm run typecheck, and npm test from the repository.

License

MIT. See the license text.