Let your AI agent drive the content engine.
theStacc ships a published MCP server with 12 tools and per-project API keys. Your agent can review the plan, draft, edit, and stage work — and publishing always waits for a human to approve.
Included with Blog SEO · plans from $99/mo· Cancel before trial ends · no charge· You stay in control
Built for operators who need publishing that ships
Outcomes this feature is built to support.
No invented case stats. Mechanisms you can verify in the product.
Your assistant, not another dashboard
Work from Claude or any MCP client. The content engine becomes something you can just ask for.
Publishing stays gated
Agents can plan, draft, edit, and stage. The publish step always requires a human approval.
Scoped keys you control
Per-project API keys are generated and revoked in-app, so access never outlives the work.
Your assistant can run the content engine.
It still can’t publish without you.
theStacc ships a published MCP server with 12 tools and per-project API keys. Claude — or any MCP client — can read your plan, draft, edit, and stage the work. The publish step stops and waits for a human, by design.
One key, scoped to one project.
Revoke it and access ends.
Generate a per-project API key in the app and point your client at the published server. stdio for assistants running on your machine, HTTP for hosted ones. The key is scoped to a single project, and revoking it cuts access immediately — no lingering session to chase.
- Published package: @thestacc/mcp-server
- stdio and HTTP transports
- Per-project keys, revoked in-app the moment you want
Ask for four posts on a theme.
Watch them land in the plan.
The 12 tools cover the real workflow, not a toy subset: read the content plan, add one to ten planned posts at a time, draft from an abstract, generate and edit a blog, regenerate a specific weak section or a single image, upload your own image. Your agent does the clicking; you stay in the conversation.
- Read the plan and add 1–10 posts at a time
- Draft from an abstract, then edit in place
- Regenerate one section or one image — not the whole article
The scary version of this product
is the one we didn’t build.
An agent with your publishing credentials and no supervision is a bad idea, so that is not what this is. Publishing is gated on human approval in the code, not in a settings toggle someone can flip at 3am. Everything else — planning, drafting, editing, staging — your agent can do all day. The same honesty and quality gates that guard the app guard the agent too.
- Publishing gated on human approval, in code
- Same honesty gates: no invented prices, codes, or quotes
- Audit trail of everything the agent changed
Part of Blog SEO →
Any client that speaks MCP — Claude among them. theStacc publishes @thestacc/mcp-server with both stdio and HTTP transports.
No. Publishing is gated on human approval by design. An agent can take a draft right up to the edge and no further.
Review the content plan, add planned posts (1–10 at a time), draft from an abstract, generate and edit blogs, regenerate sections and images, upload images, and request publish. The tools cover the Blog SEO module.
Yes. A public headless blog API lets you pull published articles, fetch by slug, and read sitemap entries with an API key — useful when you want to render content on your own stack instead of receiving webhooks.
Start free.
Ship real work.
Included with Blog SEO · plans from $99/mo. Cancel anytime before the trial ends and you won’t be charged.
Start free 3-day trial →