Papera is still under development. Things may change or break as we build.
MCPConnect your AI client

Connect your AI client

Add Papera's MCP server to Claude or another AI client, sign in once, and check that the tools are available.

Papera runs a Model Context Protocol (MCP) server, so an MCP-capable AI client (Claude, or another assistant that supports remote MCP servers) can work in your Papera account on your behalf. You describe what you want in the chat, and the client calls Papera's tools for you.

This page gets the connection working. The pages after it cover what you can do once it is connected.

1. Add the server

Server URL: https://papera.dev/api/mcp

Most clients ask only for a name and a URL when you add a remote MCP server. Where a client uses a config file, the entry looks like this:

{
  "mcpServers": {
    "papera": {
      "url": "https://papera.dev/api/mcp"
    }
  }
}

Other clients have a settings screen instead. Either way the contract is the same: a remote HTTP MCP server plus a browser sign-in. Check your client's own documentation for where it registers remote servers.

2. Sign in

You never paste a token. The first time the client calls Papera it opens a browser window, you sign in to your Papera account as usual, and the client keeps the session from then on.

Sign in with the same account you use in the app. The tools act on that account: its projects, its plan limits, its connected social accounts.

3. Check it worked

Ask your client what Papera tools it has. You should see the content tools (generate_outline, approve_outline, approve_content, save_project) alongside the workflow tools (get_workflow, add_node, attach_renderer, publish_post and the rest). If the list is there, you are connected.

A quick first run: ask for something small, such as "draft a five point deck on our onboarding flow and save it to Papera". You will be asked to approve the outline and then the content, and you will get a link to the saved project at the end.

What you can do from here

  • Create content from a topic or from text you already have, and save it as a project.
  • Build a workflow: add nodes, connect them, attach renderers and compose social posts.
  • Publish and schedule, with a confirmation step before anything leaves Papera.

If you would rather see whole runs end to end, start with a deck from your notes.

Things worth knowing

Your account, your limits. Work done over MCP counts against the same plan as work done in the app: the same project limit, the same publishing allowance, the same connected accounts.

Social accounts are connected in the app. Papera never starts an account connection over MCP. Connect Bluesky, Telegram, Instagram or LinkedIn in Settings first (see Connect a Bluesky account or Connect a Telegram channel), then refer to that connection from your client.

Nothing is published without you. Content is saved only after you approve it, and every tool that posts, schedules or otherwise reaches outside Papera shows you a plan first.

If something is not working

The client cannot sign in, or keeps asking. Confirm the URL is exactly https://papera.dev/api/mcp, and that your browser is not blocking the popup window the client opens.

The tools work but your projects are missing. You are probably signed in to a different Papera account than the one you use in the app. Sign out of the server in your client and connect again.

A tool refuses with a reason. That is by design: Papera says no rather than guessing. The message names the way forward, for example which projects you can add content to when you are at your project limit.