Create content over MCP

Turn a topic or your own notes into approved content saved as a Papera project, using Papera's models or your client's own.

Once your client is connected, you can create content without opening the app. Ask for what you want ("write me a short deck on our Q3 results"), and the client works through the tools below with you.

The result is a normal project in your account, saved on the server and open on any device you sign in on. Nothing is published by this flow.

Starting a run

Everything starts with generate_outline:

Argument	What it does
`topic`	What to create. Required unless you pass `source_text`.
`source_text`	Text you already have. Papera builds the content from it instead of researching.
`mood`	Tone: `professional`, `technical`, `educational`, `playful`, `inspirational` or `urgent`.
`theme`	A look you would like, in your own words.
`use_my_model`	Have your client's model do the writing instead of Papera's.

You can pass both topic and source_text: the topic then says what to make of the text.

Who writes: Papera's models, or yours

By default Papera researches, plans and writes on its own models, which spends AI credits on your account.

Pass use_my_model and the work is delegated to the model in your client instead. At each step Papera hands back a prompt, your client's model runs it, and submit_agent_action returns the result. Papera still plans the run, holds the approvals and saves the project. That path costs no credits, because the generation was never ours.

Apart from who writes, both paths are the same workflow with the same approval steps, so you can switch between them run to run.

The steps

generate_outline starts the run and returns an outline for you to review. With use_my_model it returns a prompt first, and your client calls submit_agent_action with what its model produced. That repeats for each step that needs the model.
approve_outline records your decision on the outline. Approving it writes the content.
approve_content records your decision on the written content.
save_project saves the approved content as a project and gives you a link to open it.

generate_outline
        │
   outline  ◄── your approval (repeatable)
        │
   content  ◄── your approval (repeatable)
        │
  save_project ──► link to your project

Papera names the next tool to call at every step, so your client does not have to guess the order.

Approving and revising

At both approval steps your client shows you the draft and asks what to do. Your answer can be:

Approve to accept the draft as it stands.
An edit to change the draft yourself.
Feedback in your own words, for example "make it shorter and add a section on pricing". Papera redoes that step and shows you the result again. Repeat as often as you like.

Nothing moves on until you approve. The outline is settled before any content is written, and the content is settled before anything is saved.

Saving

save_project returns a link like https://papera.dev/project/<id>, along with the project and workflow ids the workflow tools use. Open the link while signed in to the same account, on any device, and you land in the editor.

Pass project_id to add the content to a project you already have. It becomes a new workflow inside that project rather than a project of its own.

If you are at your project limit

Rather than picking a destination for you, save_project stops and lists the projects you already have. You can either call it again with one of those project ids, which adds the content to that project as a new workflow (workflows are not limited), or upgrade your plan for more projects.

What comes next

The saved content is a content node with nothing rendered from it yet. To turn it into a presentation, a document, a blog post or a social post, carry on with Build a workflow, or open the link and work on the flow canvas in the app.

For a full run written out, see Example: a deck from your notes.