PaperDock MCP server

• Registry namedev.paperdock/paperdockverified in the MCP registry

The registry name sits under paperdock.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-20
• Tools16
• Server calls itselfpaperdock
• Server version0.10.0
• Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 1714 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer1563 ms
• Space in an agent's context≈ 3,306 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 84 of 100

• Parameters without a description: in 15 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_projects

  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.

• create_project

  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…

• list_files

  List project file metadata without loading full file contents.

• search_files

  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…

• read_file

  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…

• read_pdf

  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…

• upload_file

  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…

• create_file

  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.

• edit_file

  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…

• rename_file

  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…

• move_file

  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…

• list_comments

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

• create_comment

  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…

• reply_to_comment

  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…

• list_chat_messages

  Read recent project chat messages in chronological order.

• send_chat_message

  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…