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.
Codex, Gemini, and other MCP-capable assistants can connect too.
Connection guides last updated .
PaperDock MCP connects ChatGPT, Claude, Codex, Gemini, and other MCP-capable AI assistants to the LaTeX projects in your PaperDock account. You connect once with PaperDock OAuth, then your assistant can discover every project currently available to you without separate project-by-project setup. New projects and projects shared later appear without reconnecting. The connection follows the same Owner, Editor, and Viewer permissions as the web app, so an assistant can only use actions already available to you. Depending on your role, it can inspect projects, read and edit LaTeX files, upload binary assets, and participate in Comments and project Chat. Open the same project in the web app to compile PDFs, manage members, restore file history, or perform other high-impact actions. Revision checks help prevent accidental overwrites, and AI agent connections are always free. You can revoke the connection at any time.
Choose the assistant you already use and follow the steps shown for that environment.
Follow these steps in order.
Open Plugins in ChatGPT.
Search for "PaperDock" and select Install. PaperDock is available as an official ChatGPT plugin.
Choose one of the following options.
paperdockhttps://app.paperdock.dev/api/mcpOAuthSwitch to your Personal workspace, search for "PaperDock" in Plugins, and select Install.
If Developer mode is also disabled by your administrator, PaperDock requires administrator approval in this workspace.
Sign in to PaperDock and select Allow when prompted.
Verify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.Sign in to the PaperDock account you want in your browser.
Open Plugins -> PaperDock.
Select Uninstall, then reinstall PaperDock.
Follow these steps in order.
Open a terminal.
Add PaperDock.
codex mcp add paperdock --url "https://app.paperdock.dev/api/mcp"If the sign-in window did not open, run this command.
codex mcp login paperdockStart Codex.
codexVerify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.Sign in to the PaperDock account you want in your browser.
Open a terminal and run:
codex mcp login paperdockFollow these steps in order.
Open a terminal.
Add PaperDock for your Claude user account.
claude mcp add --transport http --scope user paperdock https://app.paperdock.dev/api/mcpStart Claude Code.
claudeOpen MCP settings inside Claude Code and authenticate PaperDock.
/mcpVerify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.Sign in to the PaperDock account you want in your browser.
In Claude Code, run:
/mcpSelect paperdock, then choose Clear authentication.
If PaperDock is still connected, select Disconnect, then Connect again.
Follow these steps in order.
Open Customize -> Connectors.
Select + -> Add custom connector.
Enter the connector name.
paperdockEnter the remote MCP server URL.
https://app.paperdock.dev/api/mcpSelect Add or Connect, then sign in to PaperDock.
Verify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.Sign in to the PaperDock account you want in your browser.
Open Settings -> Connectors -> PaperDock.
Select Disconnect, then Connect.
Follow these steps in order.
Open Customize -> Connectors in Claude.
Select + -> Add custom connector.
Enter the connector name.
paperdockEnter the remote MCP server URL.
https://app.paperdock.dev/api/mcpSelect Add or Connect, then sign in to PaperDock.
Verify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.Sign in to the PaperDock account you want in your browser.
Open Settings -> Connectors -> PaperDock.
Select Disconnect, then Connect.
Remote connectors belong to your Claude account. If PaperDock is already connected in Claude Web with the same account, you do not need to add it again.
Follow these steps in order.
Open a terminal.
Add PaperDock for your Gemini user account.
gemini mcp add --transport http --scope user paperdock https://app.paperdock.dev/api/mcpStart Gemini CLI.
geminiAuthenticate PaperDock inside Gemini CLI.
/mcp auth paperdockVerify the connection in your AI assistant.
Show my PaperDock projects to confirm the connection.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.
Begin with these requests with your AI assistant. 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 Comments and Chat. Reply to the Comments I have already added with your thoughts.
Read main.tex, improve the abstract, and apply the edit. Tell me exactly what you changed.
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, comment, chat, and compile in the browser.
Let your AI agent list PaperDock projects, inspect file trees, search LaTeX source, read text, and retrieve assets from the tools you already use.
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.
Open the same project in PaperDock to compile PDFs, inspect file history, manage files and members, and resolve Comments with full project context.
Ask your agent to read active Comments, add one to a passage in a .tex file, reply to it, and join the same project Chat your collaborators use on the web.
PaperDock applies MCP text edits to the shared file immediately and records each one for Review changes. In the web app, inspect the inline Diff, keep or revert individual changes, edit changed lines, move between changed files, or keep or revert the full file.
Ask your agent to read the current file before editing. Revision checks reject stale edits, so the agent must read the latest content again instead of overwriting newer work.
Text edits and binary replacements use current revision context. If a file has changed, the agent must read it again. Full file history and revision restore remain in the web app.
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.
Any connected user can list accessible projects and create a new PaperDock project. All three project roles can use Comments and Chat; only Owners and Editors can modify files. Comment resolution and deletion, file history, and compilation stay in the web app.
PaperDock keeps its public MCP surface focused and predictable. Use the web app when you need to perform these actions.
Open the item that matches what you are seeing.
Use the client-specific tab above. In ChatGPT, open Plugins and search for PaperDock. In Claude, open Customize, then Connectors. For Codex, Claude Code, or Gemini CLI, run the command shown in its tab. Managed workspaces may restrict plugin or connector controls; if ChatGPT shows "Disabled by admin," open the fallback options in the ChatGPT guide.
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.
PaperDock checks your current role on every tool call. A Viewer cannot change project files, and a recent role change applies to an existing connection immediately. Project compilation is not exposed through MCP for any role. Ask the project Owner to review your role in the web app.
Reauthentication can be needed after a disconnect, revoked access, or a long period of inactivity. Open Change connected PaperDock account in the relevant guide above and follow that client's current reconnect steps.
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].
Most users can stop after the connection guide. These details are available for MCP clients, administrators, and directory review.
https://app.paperdock.dev/api/mcpdev.paperdock/paperdocklist_projects create_project
list_files search_files read_file upload_file replace_file create_file edit_file
list_comments create_comment reply_to_comment
list_chat_messages send_chat_message
New projects and projects shared with you appear through the same connection. PaperDock continues to check your current access.