mcp-overleaf
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_OVERLEAF_CONFIG | No | Path to the server configuration file, if a non-default config path was used during `configure`. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| connector_statusA | Check configuration, Overleaf access, Git state, and the active workflow without revealing credentials. |
| workflow_statusA | Return the active edit session, allowed next actions, preview, conflicts, and recovery journal. |
| begin_edit_sessionA | Synchronize Git and Overleaf, detect baseline conflicts, and return the sessionId required by report tools. |
| list_report_filesA | List report files in an active synchronized edit session. |
| read_report_fileA | Read a UTF-8 report source and return the SHA-256 precondition required for a safe write. |
| write_report_fileA | Write UTF-8 content only inside an active session and only when expected_sha256 matches. Use "new" for a new file. |
| preview_publishA | Perform a three-way comparison and return a previewToken, or block on same-file conflicts and deletions. |
| confirm_publishB | Revalidate the preview, commit and push Git first, upload only approved files, and verify Overleaf afterward. |
| abort_edit_sessionA | Close a session only when it has no pending local edits. This tool never reverts or deletes files. |
| compile_reportB | Compile the configured remote project and save its PDF inside the configured workspace. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target clearly distinct actions across session, file, compile, and publish workflows. The only minor ambiguity is between connector_status and workflow_status, both of which report state but from different perspectives.
The majority of tool names follow a clear verb_noun pattern like begin_edit_session, read_report_file, and confirm_publish. The exceptions are connector_status and workflow_status, which use an object_status pattern, creating a small inconsistency.
Ten tools is well-scoped for a Git-to-Overleaf synchronization and publishing workflow. Each tool contributes a distinct step in the lifecycle without unnecessary redundancy.
The core workflow is well covered: session lifecycle, file read/write, compilation, preview, and publish confirmation are all present. Minor gaps include no explicit delete-file or conflict-resolution tool, though the write tool and status reporting partially mitigate this.