PaperDock

Use your your AI on LaTeX editor

PaperDock helps researchers work on private LaTeX projects through your AI. Create projects, search and edit source files, add text files, rename or move individual files, retrieve existing compiled PDFs, and collaborate through Comments and Chat.

What you can ask

Create a project named "My Paper", then list my projects.
Example path →

MCP connector

Server URL: https://app.paperdock.dev/api/mcp
Login: OAuth
Protocol: MCP 2025-06-18
Instructions: PaperDock exposes projects according to the connected account's current PaperDock memberships and roles. Start with ; a successful response confirms the connection. Use the exact projectId in every project tool call, ask the user when the target is ambiguous, and keep projectId out of user-facing responses unless explicitly requested. Use to inspect paths, when the requested word, phrase, citation key, label, command, or other text may appear in unknown files, and directly when the target file is already known. For a localized task in a large text file, use .lineRange to load only the needed lines. Read the relevant current text before editing it and pass the returned baseRevision to . For a long replacement that covers complete source lines, refine lineRange to exactly those lines and pass its rangeToken with insert; this avoids retyping the old text. Otherwise use guarded operations for focused edits, with the exact unmodified expectedText at each sequential UTF-16 range. Never retype, normalize, spell-correct, or manually Unicode-escape expectedText. Use full content only for broad rewrites. If a revision, target, or range-token conflict occurs, read the relevant current text again and retry once; do not repeat reconstructed text or guessed offsets. Edit multiple files sequentially with , and if a later edit fails, stop and report which earlier files were already changed. Use only for new editable text paths and for existing text. Binary uploads and replacements must be performed directly by the user in the PaperDock web app; never recreate the asset under another path or extension. Use with an explicit entry .tex path to retrieve an already compiled PDF; it never compiles or waits. Respect the returned freshness and latest compile status, and download and open the PDF before describing its contents or layout. If your client cannot inspect PDFs, say so. Project rename/delete, member management, file deletion, folder move/copy, file-history access or revision restore, comment resolution or deletion, and project compilation are intentionally not exposed. Ask the user to perform those actions in the PaperDock web app and never simulate them by emptying, overwriting, copying, recreating, or otherwise modifying related content. Create a project only when the user explicitly asks. On PROJECT_NAME_ALREADY_EXISTS, do not retry with the same name or a case/whitespace-only variant. Call to find the existing project. If the user's intent is unclear, ask whether to use that project or create a new one with a different name. Never modify the existing project or choose a different name without the user's authorization. Use or only when the user requests a file rename or move. Both support existing text and binary files without reading or copying their contents. Call first and pass the exact path and its revision as baseRevision. preserves the directory and extension; preserves the filename within the same project. No overwrites, folder moves, cross-project transfers, or binary content changes are allowed. Path changes apply immediately, outside Review changes Keep/Revert. Text references are not automatically updated: check relevant LaTeX and bibliography references (including relative paths inside a moved text file), use guarded if needed, and report any incomplete reference updates separately. On a missing path or revision conflict, call and confirm the target before retrying once.

Tools

Reads data7

Changes data3

Deletes or can't be undone6

Skills

None in the store listings or on the server

What you can ask

Create a project named "My Paper", then list my projects.

Example path →

MCP connector

Server URL

https://app.paperdock.dev/api/mcp

OAuth

Protocol

MCP 2025-06-18

Instructions

PaperDock exposes projects according to the connected account's current PaperDock memberships and roles. Start with ; a successful response confirms the connection. Use the exact projectId in every project tool call, ask the user when the target is ambiguous, and keep projectId out of user-facing responses unless explicitly requested. Use to inspect paths, when the requested word, phrase, citation key, label, command, or other text may appear in unknown files, and directly when the target file is already known. For a localized task in a large text file, use .lineRange to load only the needed lines. Read the relevant current text before editing it and pass the returned baseRevision to . For a long replacement that covers complete source lines, refine lineRange to exactly those lines and pass its rangeToken with insert; this avoids retyping the old text. Otherwise use guarded operations for focused edits, with the exact unmodified expectedText at each sequential UTF-16 range. Never retype, normalize, spell-correct, or manually Unicode-escape expectedText. Use full content only for broad rewrites. If a revision, target, or range-token conflict occurs, read the relevant current text again and retry once; do not repeat reconstructed text or guessed offsets. Edit multiple files sequentially with , and if a later edit fails, stop and report which earlier files were already changed. Use only for new editable text paths and for existing text. Binary uploads and replacements must be performed directly by the user in the PaperDock web app; never recreate the asset under another path or extension. Use with an explicit entry .tex path to retrieve an already compiled PDF; it never compiles or waits. Respect the returned freshness and latest compile status, and download and open the PDF before describing its contents or layout. If your client cannot inspect PDFs, say so. Project rename/delete, member management, file deletion, folder move/copy, file-history access or revision restore, comment resolution or deletion, and project compilation are intentionally not exposed. Ask the user to perform those actions in the PaperDock web app and never simulate them by emptying, overwriting, copying, recreating, or otherwise modifying related content. Create a project only when the user explicitly asks. On PROJECT_NAME_ALREADY_EXISTS, do not retry with the same name or a case/whitespace-only variant. Call to find the existing project. If the user's intent is unclear, ask whether to use that project or create a new one with a different name. Never modify the existing project or choose a different name without the user's authorization. Use or only when the user requests a file rename or move. Both support existing text and binary files without reading or copying their contents. Call first and pass the exact path and its revision as baseRevision. preserves the directory and extension; preserves the filename within the same project. No overwrites, folder moves, cross-project transfers, or binary content changes are allowed. Path changes apply immediately, outside Review changes Keep/Revert. Text references are not automatically updated: check relevant LaTeX and bibliography references (including relative paths inside a moved text file), use guarded if needed, and report any incomplete reference updates separately. On a missing path or revision conflict, call and confirm the target before retrying once.