Claude Cowork for Marketing Ops: What the Marketing Plugin Does, and What It Still Cannot See
At some point this year your CEO forwarded you a link to Claude Cowork with the message “have you tried this?” You installed the Marketing plugin in ten minutes. You ran the campaign-plan command, got a genuinely good plan, and felt the thing marketing leaders feel when a tool exceeds expectations. Then you opened Cowork the following week to continue the campaign, and it had no idea the campaign existed.
That is not a bug in the plugin. It is what the plugin is: a set of skills and connectors that produce excellent work inside one session. What it does not have is a system that holds your plan, your calendar and your automations as live state between sessions. This post covers what the plugin ships as of September 2026, what it is good at, why the plan dies in week two, and the single addition that fixes it.
What the Marketing plugin actually ships
Anthropic launched plugins for Cowork at the end of January 2026, covered by TechCrunch at the time, and the Marketing plugin page describes what is in the box. The plugin adds a set of commands to Cowork:
/campaign-planfor a full campaign plan from a goal and audience/draft-contentfor a piece in a stated format and voice/brand-reviewto check a draft against brand guidelines/competitive-briefto pull together what competitors are saying/performance-reportto summarize results from connected analytics/seo-auditfor a page or a set of pages/email-sequencefor a multi-step email series
It works with a set of connectors, including Slack, Canva, Figma, HubSpot, Amplitude, Ahrefs and Klaviyo, and the page is explicit that the plugin does not send campaigns. Anthropic is clearly pointing this at teams like yours: it runs webinars on Claude for marketing ops and analytics and has written up how its own marketing team uses Claude.
What it is good at
Credit first, because the plugin earns it. The commands are well designed for jobs that start and finish in one sitting.
Briefs and plans. /campaign-plan with a clear goal and an audience produces something a team of three would take a day to write. /competitive-brief with Ahrefs connected turns an afternoon of tab-hopping into a document.
Drafting with review. /draft-content followed by /brand-review is a real workflow: draft, check against the guideline doc, fix. For a team without an editor it is the closest thing to one.
Reporting. /performance-report reading from Amplitude or HubSpot produces a first draft of the monthly update that is mostly right, with numbers you should still check.
Handoffs to design. Canva and Figma connectors mean the draft can leave the chat as a design file rather than a paste.
Reviewers agree on the shape of the strength. Techsy’s assessment of Cowork for marketing ops calls it excellent for tasks that fit in one session, and the Substack guides that have appeared since launch, such as the marketer’s guide to Cowork plugins, are mostly lists of one-session wins.
The week-two problem
The same Techsy review names the limit in one line: Cowork is bad at tracking a campaign over the next six weeks. That is the whole problem, and it is worth being precise about why.
Look at the connector list again. Slack, HubSpot, Amplitude, Ahrefs, Klaviyo are inputs: the plugin reads from them. Canva and Figma are file outputs: the plugin writes a design. What is missing is a system that holds the campaign itself: the plan as an object, the pieces with their send days, the calendar they sit on, the follow-up automation with its steps, and the queue where a person approves each piece. Brand guidance, likewise, lives in the plugin’s local settings rather than in a system of record that the rest of your marketing uses.
So /campaign-plan produces a beautiful document, and the document goes in a folder. In week two you open Cowork, and there is no object to pick up. You can paste the document back in, and the plugin will happily continue, but now you are the state machine: you remember what launched, what moved, what is still in draft. The plan is wherever you last left it. There is a general version of this argument in why a marketing knowledge base is not enough for AI agents: documents make an assistant informed; only a system connection makes it useful across time.
What is missing is a system, not a skill
The instinct when a tool stalls is to add another skill or a longer prompt. Here the missing piece is a place for the work to land. The table shows where each command’s output goes today and where it should go.
| Command | Where the output lands today | Where it should land |
|---|---|---|
/campaign-plan | A document in the chat or a folder | A campaign draft with pieces and send days on the calendar |
/draft-content | Text in the chat, or a Canva or Figma file | A content draft attached to the campaign, waiting for approval |
/email-sequence | A document listing the emails and their timing | An automation draft with per-step timing and quiet hours |
/brand-review | Comments in the chat | Suggestions anchored to the exact sentences in the draft |
/performance-report | A document | Fine as a document; reports are one-session work |
/competitive-brief | A document | Fine as a document, feeding the next plan |
The right column is what an MCP connector to a marketing system provides. Marqeable’s connector, as one example, holds business context (brand, ICP, voice, offers), campaigns with their pieces and send days, semantic search over existing content, the content calendar with scheduled sends and market dates, and every automation with its plan. Its write tools create campaign drafts, content drafts, anchored suggestions on existing copy, brief updates and automation drafts. Every write is a draft. There is no send, launch, publish or delete tool, which is what makes it safe to run inside a plugin that Anthropic has already promised will not send campaigns.
One more connector, and the plan persists
Custom connectors added in Claude are available in Cowork, per Anthropic’s custom connector guide. Here is the first session with the Marketing plugin and Marqeable both on. The plugin command does the planning; the connector does the landing.
You: /campaign-plan for a Q4 push on the 30-day pilot, aimed at first controllers at 50 to 200 person companies. Read my business context and the calendar first.
Claude: Business context confirms the pilot offer and the voice guide. The calendar has a nurture email on the 4th, the webinar reminder on the 16th and a LinkedIn case study on the 18th. Here is the plan: five pieces over three weeks starting the 8th, avoiding the 16th and 18th, with a closing email ahead of quarter close. [Plan follows.]
You: Good. Now create this as a campaign draft in Marqeable with the pieces on the calendar.
Claude: Created a campaign draft, “Q4 pilot for controllers”, type nurture, starting the 8th, standard volume, with five content drafts attached on days 0, 2, 9, 11 and 16, copy only. Nothing is scheduled to send. It is waiting for your review: [link to the campaign in Marqeable].
And the second session, a week later:
You: Where are we on the Q4 pilot campaign?
Claude: From Marqeable: the campaign is in draft with five pieces. You approved the day-0 and day-2 pieces on Tuesday; the day-9 email is still in review with one open suggestion on the subject line; days 11 and 16 are untouched. The calendar shows the day-0 email placed on the 8th as planned.
That second exchange is the one the plugin alone cannot have. The state lived in a system, so the next session picked it up without a paste. The same approach turns /email-sequence into an automation draft with real timing and turns /brand-review into suggestions anchored to specific sentences rather than notes in a chat.
Keep the plugin for what it is good at: planning, drafting, review and reporting inside a session. Add one connector so the plan, the pieces and the follow-up land as drafts in a system that remembers them. The plugin thinks; the system holds; you approve.
Approval modes, and why draft-only matters here
Cowork lets you choose how tool calls are approved. Anthropic’s guide to using Cowork safely describes manual approval, automatic approval and skipping, and recommends staying on manual for actions that would be hard to undo, with sending messages as the example. It also advises against scheduling tasks that send on your behalf.
That advice sorts connectors into two kinds. A connector with a send tool should stay on manual approval forever, and should never be in a scheduled task. A connector whose every write is a draft can safely run on automatic approval, because the worst outcome of any call is a draft in your queue. This is the distinction that lets Cowork do more than one session’s work without a person clicking approve on every tool call; the full argument is in the draft-only rule.
Adding Marqeable to Cowork
The server is https://app.marqeable.com/mcp, a remote MCP server over HTTP with OAuth 2.1. You sign in with your normal Marqeable login in a browser window and Claude sees exactly what your account can see. No API keys are involved.
In Claude, open Settings > Connectors, click Add custom connector, name it “Marqeable”, paste the address, click Add, then Connect and sign in. On Team or Enterprise plans an Owner adds it under Organization settings and each member clicks Connect. Once it is added, enable it in the Cowork session alongside the Marketing plugin. A good first prompt is “Run whoami, then get_business_context, then tell me what is on the calendar this month.” If you would rather Claude prepared the week’s drafts on a schedule, the routine version of this setup is in Claude Code Routines for marketing, and the weekly-plan pattern it fits into is in the AI marketing agent’s weekly plan.
Frequently asked questions
What does the Claude Cowork Marketing plugin do?
As of September 2026 it adds a set of marketing commands to Cowork, including campaign planning, content drafting, brand review, competitive briefs, performance reports, SEO audits and email sequences, and it connects to tools such as Slack, Canva, Figma, HubSpot, Amplitude, Ahrefs and Klaviyo. Anthropic states that it does not send campaigns.
Why does Cowork lose track of my campaign after the first session?
Because the plugin’s connectors are inputs, such as analytics and CRM data, or file outputs, such as design tools. Nothing it connects to holds the plan, the calendar and the automations as live state, so the next session starts without knowing what you launched in the last one. The output of a planning command is a document, not a campaign.
Can I add my own connector to Cowork?
Yes. Custom connectors added under Settings > Connectors in Claude are available in Cowork sessions. Adding a marketing-system connector such as Marqeable lets the plugin’s plan land as a campaign draft that persists between sessions and waits for your approval.
Is it safe to let Cowork approve tool calls automatically?
Anthropic advises manual approval for actions that would be hard to undo, such as sending messages. Automatic approval is reasonable only for connectors whose every write is a draft. Marqeable’s connector has no send, launch, publish or delete tool, so the worst outcome of an automatic call is a draft in your review queue.
The bottom line
The Marketing plugin is the best one-session marketing assistant most teams have used, and the plan it produces in ten minutes is real. What it lacks is a place for that plan to live: its connectors read from analytics and CRM and write to design files, and nothing holds the campaign, the calendar and the follow-up between sessions. Add a marketing-system connector whose every write is a draft, and week two starts where week one left off, with the approval still yours.
See the persistent half live: Marqeable’s agents build and run your campaigns, run behavior-triggered automations across text and email, answer and qualify every visitor with AI website chat, and tie revenue to the exact message with attribution.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
