PaperDock

Create an open Comment on a .tex project file and post it immediately to project collaborators without changing the source file. Later deletion cannot undo prior delivery or reading. Selection offsets may be inferred from quote. Provide exactly one target: fileId or path.

Immediately edit one existing editable text file and record the applied change in PaperDock's Review changes UI. Provide exactly one target (fileId or path) and exactly one payload: operations, content, or rangeToken with insert. Read the relevant current text first and pass its baseRevision. For a long replacement covering every line returned by an exact read_file.lineRange call, pass its rangeToken with insert; the token is connection-, file-, revision-, range-, and content-bound and expires after 10 minutes. For other focused edits, use sequential UTF-16 operations and copy expectedText exactly from read_file without retyping, normalization, spelling correction, or manual Unicode escaping; insertions use expectedText: "". On a conflict, read again and retry once. Use content only when broadly rewriting most of the file. This tool cannot create, rename, or delete files.

Move one existing text or binary file to a project-relative folder in the same project, preserving its filename and contents. Use an empty destinationFolder for the project root. New implicit folders are allowed. Use rename_file or move_file only when the user requests a file rename or move. Both support existing text and binary files without reading or copying their contents. Call list_files first and pass the exact path and its revision as baseRevision. rename_file preserves the directory and extension; move_file 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 edit_file if needed, and report any incomplete reference updates separately. On a missing path or revision conflict, call list_files and confirm the target before retrying once.

Rename one existing text or binary file in its current folder, preserving its extension and contents. Use rename_file or move_file only when the user requests a file rename or move. Both support existing text and binary files without reading or copying their contents. Call list_files first and pass the exact path and its revision as baseRevision. rename_file preserves the directory and extension; move_file 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 edit_file if needed, and report any incomplete reference updates separately. On a missing path or revision conflict, call list_files and confirm the target before retrying once.

Post a reply under the connected PaperDock account, marked as created via an AI agent, immediately to an open Comment. Use a commentId returned by list_comments or copied from PaperDock. If a Comment is not found, call list_comments once and do not retry the same missing commentId. It is visible to project collaborators, and later removal cannot undo prior delivery or reading. Write body as natural, collaborator-facing prose.

Post a message under the connected PaperDock account, marked as created via an AI agent, immediately to the selected private PaperDock project's Chat. It is visible to project members, and later editing or deletion cannot undo prior delivery or reading.

Create a new editable text file at a new project path from supplied content. Pass an explicit empty string to create an empty file. Existing paths are never overwritten.

Create a new PaperDock project with a starter main.tex only when the user explicitly asks. Names are unique per owner, ignoring letter case and leading/trailing spaces. On PROJECT_NAME_ALREADY_EXISTS, do not retry create_project with the same name or a case/whitespace-only variant. Call list_projects 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.

Create one new editable text file from UTF-8 content. For compatibility contentBase64 is accepted only for UTF-8 text at an editable extension. Existing paths are never overwritten; use edit_file for existing text. Binary uploads and replacements are not supported by MCP: ask the user to upload or replace images, PDFs, and other binary assets directly in the PaperDock web app. Do not recreate them under another path or extension.

Read recent project chat messages in chronological order.

List active project comments and their replies. Resolved comment history is not returned by this tool.

List project file metadata without loading full file contents.

List standard PaperDock projects accessible to the connected account, including its current role and effective MCP capabilities for each. Use projectId only for subsequent tool calls and do not show it unless explicitly requested.

Read an editable project file or return a 10-minute signed download URL for a private project asset. Provide exactly one target: fileId or path. For a localized task in a large text file, pass lineRange with inclusive 1-based startLine and endLine values to return at most 400 lines, absolute UTF-16 offsets, and a revision-bound rangeToken. If replacing all returned source lines, pass that rangeToken to edit_file instead of retyping the old text. Refine lineRange first when only part of the returned range should change. Omit lineRange when the full file is required.

Get the latest successful compiled PDF for an explicit entry .tex path, with a signed download link valid for at most 10 minutes, size, generation time, and freshness information. This never compiles, waits, or polls. A newer running or failed compile may coexist with an older successful PDF. Freshness is unknown unless later source changes are detected; never assume the PDF matches current or unsaved source. Download and open the PDF using a PDF-capable tool before discussing its contents or layout; a link alone is not a PDF inspection. If no result exists or it has expired, ask the user to compile in the web app. Use read_file for uploaded PDF assets.

Find where a word, phrase, citation key, label, LaTeX command, or other text appears across editable project files when its file or location is unknown. Search is case-insensitive and returns matching paths, positions, revisions, and short snippets. If the target file is already known, use read_file directly instead.