The Gap Between Deciding and Doing
You decide to make content constantly. In meetings, in Slack, while reviewing a competitor's launch. The decision never arrives at a moment when you can stop and produce the asset.
So the intent gets parked in a note, a ticket system that knows nothing about content creation, or memory. By the time you sit down to create, the context that made the idea sharp is gone.
A Brief That Executes Itself
A plan is a pre-loaded content-creation form plus planning metadata. Capture 1 in 10 seconds with just a title, or carry a full brief: the prompt, the blueprint, the project, reference documents, targeting, an assignee, a due date.
Come back later, tomorrow or next month, and everything is exactly where you left it. Click Generate, or hand it to the agent.
AI Proposes, You Decide
Every plan moves through 5 stages. Things you asked for start at Accepted. Things the agent or a workflow proposed start at Suggested and wait for your review. Select a stage.
Proposed by the agent or a workflow. Waiting for your review, nothing is generated yet.
A suggestion you pass on leaves the queue cleanly. Nothing gets generated without your go.
Added by you, requested through the agent, proposed unprompted, or generated by a workflow, each with a link back to the origin: the Asana task, the meeting transcript, the workflow run.
Your Queue Fills Itself
Set a workflow to watch the places requests come from: connected apps like Asana and Microsoft Teams, meeting transcripts, your own product calendar. When it spots a content opportunity, it proposes a plan into the Suggested queue.
You stay the editor-in-chief. Review what arrived, accept what is worth making, dismiss the rest.
2 Ways to Fire a Plan
The form's current state goes directly to generation. The brief you staged is the brief that runs, no re-entry, no reassembly.
The Marcora Agent opens knowing everything the plan knows. Refine the prompt, ask for research, then either the agent creates the content or writes its improved brief back to the form for you to fire.
Your Best Sequence, Saved as a Play
A playbook is an ordered set of plan templates: a product-launch play, a webinar promotion sequence, a monthly newsletter cycle. Run it against a project with an anchor date and every plan lands dated relative to that anchor. Reusable, shareable with the team, and every run creates a tracked cycle.
Completion That Cannot Lie
A plan never has its own done checkbox. When the content it produced reaches Ready, the plan completes automatically.
So the queue always tells the truth. Planning and reality cannot drift apart, because completion is measured by the content actually shipping.
The Whole Loop, From Whatever Tool You Work In
Connect the Marcora MCP server and the complete plan-to-content loop runs from Claude, ChatGPT, Cursor, or any MCP-compatible AI tool. Add ideas to the queue, review and update the briefs as they move through stages, generate the content from an accepted plan (the exact same action as the Generate button), save a batch of plans that worked as a reusable playbook, and run a playbook anchored to a date to kick off a whole dated cycle. Not read-only access, the full loop.
The Marcora Agent itself runs on the exact same server customers connect to, so your AI tools get the same tools our agent uses, nothing held back.
The queue lives in Marcora, and that is where the review-and-go experience is at its best.
Park the Idea Where It Can Fire
Creating and reviewing plans is free. Generating the content uses Studio Credits, like any generation.
Frequently asked questions
What happens when the agent suggests something?
It lands in the Suggested queue with its source attached and waits. Nothing is generated until you review it and accept. Dismiss it and it leaves the queue cleanly.
Can my team see what is planned?
Yes. The queue is a shared surface: plans carry assignees, due dates, and stage badges, so everyone sees what is staged, what is in process, and what shipped.
What is a playbook vs a project?
A project is the container for real work in flight. A playbook is a reusable template, an ordered set of plan templates you run against a project with an anchor date. The run stamps dated plans into that project as a tracked cycle.
Does a plan cost credits before I generate?
No. Creating, staging, and reviewing plans is free. Studio Credits are only used when you generate the content, like any generation.
Can I use plans from outside Marcora?
Yes, the complete loop. From Claude, ChatGPT, Cursor, or any MCP-compatible AI tool you can add ideas, update briefs, generate content from an accepted plan, save playbooks, and run them anchored to a date. The review-and-go experience is at its best in Marcora itself.
