PaperDock

Connect AI Agent

Connect PaperDock once to use every project you can access.

Codex CLI

Follow these steps in order.

  1. Open a terminal.

  2. Add PaperDock.

    Commandcodex mcp add paperdock --url "https://app.paperdock.dev/api/mcp"

  3. Sign in to PaperDock.

    Commandcodex mcp login paperdock

  4. Start Codex.

    Commandcodex

Why PaperDock asks you to sign in

Sign-in connects the AI environment to your PaperDock account so PaperDock can check your current project memberships and roles. You sign in on PaperDock's domain, and the AI environment receives an OAuth authorization rather than your sign-in credentials. You can deny the request or disconnect and authorize again later. The AI provider you choose processes project information you ask it to use under that provider's own terms and privacy policy.

Try it right away

Begin with these requests with your AI assistant.

Copy an example into your AI assistant, then replace the project name or task with your own.

Create a PaperDock project named Research Draft. We'll use this project for the rest of our work.
Read main.tex and propose a clearer abstract.
Read main.tex and leave your suggestions in Reviews and Chat. Reply to the Reviews I have already added with your thoughts.
Compile the project and help me understand any LaTeX errors in the latest job.
What you can do

Connect your local workspace to web collaboration.

Use Codex, Claude Code, Gemini CLI, or another MCP-capable agent from the environment where you already work. PaperDock keeps the same project available for your team to edit, review, chat, and compile in the browser.

Work from your local environment

Let your AI agent list PaperDock projects, inspect file trees, search LaTeX source, read text, and retrieve assets from the tools you already use.

Edit the shared web project

Create or update one or several LaTeX files, upload new files, and replace assets in the same PaperDock project your team uses in the browser.

Compile from your AI agent

Start a PaperDock compile, check its status and logs, and retrieve the resulting PDF while your team continues working online.

Continue through Reviews and Chat

Ask your agent to read or create Reviews, reply or resolve them, and join the same project Chat your collaborators use on the web.

Review and control

Stay in the loop when an agent edits LaTeX.

When an eligible PaperDock workspace is open, it can claim an agent text proposal and show it as an inline Diff. You can accept, decline, or revise individual changes and move between changed files.

Keep the web workspace open when you want to review edits inline before they are applied. If no eligible web client claims the proposal during the review window, PaperDock's normal auto-apply policy may be used.

Revision context protects current work

File edits and binary replacement use current revision context. Agents can also list visible text history, and Owners or Editors can restore a listed revision through the normal review flow.

Permissions

The same project role follows you into MCP.

Effective access is the intersection of OAuth permission, your current PaperDock role, and PaperDock's MCP safety policy. Role changes and membership removal take effect on the existing connection.

RoleWhat the connected agent can do
OwnerRead and edit files, upload assets, compile, restore history, rename the project, and use Reviews and Chat.
EditorRead and edit files, upload assets, compile, restore history, and use Reviews and Chat.
ViewerList, search, and read project files and visible history. Viewers can also read and contribute to Reviews and Chat, but cannot edit files or compile.

All three roles can read and send Chat messages and can create, reply to, and resolve active Reviews. Owners and Editors can delete any active Review; a Viewer can delete only a Review they authored.

Kept in the web app

High-impact actions stay where context is visible.

PaperDock intentionally does not expose the following actions through MCP. Use the web app when you need to perform them.

Help

Most connection problems have a short fix.

Open the item that matches what you are seeing.

I cannot find an MCP or connector menu.

Check your AI provider's current plan and workspace permissions. Custom MCP connections are not available in every plan or managed workspace.

My projects do not appear.

Confirm that you approved the same PaperDock account that owns or belongs to the project. Ask the agent to list PaperDock projects again; new and newly shared projects appear without reconnecting.

The agent says I do not have permission.

PaperDock checks your current role on every tool call. A Viewer cannot edit or compile, and a recent role change applies to an existing connection immediately. Ask the project Owner to review your role in the web app.

I am asked to sign in again.

Reauthentication can be needed after a disconnect, revoked access, or a long period of inactivity. Start the connection flow again and approve PaperDock in the account you want to use.

An older PaperDock connection no longer works.

Remove the old connection and reconnect with the account-level URL shown in the guide above. Do not add a project ID or other query parameters to the URL.

Still stuck? Contact PaperDock at [email protected].

Technical reference

Connection details for clients and reviewers.

Most users can stop after the connection guide. These details are available for MCP clients, administrators, and directory review.

Name
PaperDock MCP
MCP URL
https://app.paperdock.dev/api/mcp
Transport
Streamable HTTP
Authentication
PaperDock OAuth with PKCE S256
Connection scope
One PaperDock account, with current project memberships
Official Registry name
dev.paperdock/paperdock
View all available MCP tools

Projects

list_projects create_project get_project rename_project get_project_context

Files

list_files search_files read_file upload_file replace_file create_file write_file apply_patch apply_changeset

Compile

compile_project get_compile_job

Reviews and Chat

list_reviews create_review reply_to_review resolve_review delete_review list_chat_messages send_chat_message

History

list_file_revisions restore_file_revision

Connect once. Keep working as projects change.

New projects and projects shared with you appear through the same connection. PaperDock continues to check your current access.

Open PaperDock