papergraph-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_environment_diagnosticsB | Return PaperGraph version and reproducible launch diagnostics. |
| validate_arxiv_inputC | Normalize arXiv ID and URL inputs and return the safe next action. |
| validate_arxiv_requestB | Validate a raw user arXiv request and return the safe next action. |
| open_workspaceC | Open or initialize a persistent multi-paper workspace. |
| workspace_add_local_paperB | Add or replace a local LaTeX project in the active workspace. |
| workspace_add_arxiv_paperB | Add or replace an arXiv LaTeX project in the active workspace. |
| workspace_add_pdf_paperC | Add or replace a born-digital PDF paper in the active workspace. |
| workspace_list_papersB | List all papers stored in the active workspace. |
| workspace_get_paperA | Return metadata and counts for one stored paper. |
| workspace_search_theoremsB | Search theorem titles and bodies across the active workspace. |
| workspace_get_dependenciesC | Return dependencies of a globally identified stored theorem. |
| workspace_get_dependency_diagnosticsC | Explain how workspace dependencies were extracted for one theorem. |
| workspace_get_citationsC | Return incoming or outgoing citation evidence for a stored paper. |
| workspace_list_resultsC | List stored evidence results across the active workspace. |
| workspace_get_resultB | Return one stored evidence result with source spans. |
| workspace_get_result_proofC | Return proof evidence for one stored evidence result. |
| workspace_get_proof_dependenciesC | Return proof dependency evidence for one stored evidence result. |
| workspace_get_external_result_mentionsB | Return external result mentions from a result's proof evidence. |
| workspace_get_evidenceC | Return metadata and source spans for one evidence node or edge. |
| workspace_export_reading_bundleC | Export a paper-level evidence bundle for paper-reading consumers. |
| workspace_export_result_reading_contextB | Export focused evidence context for reading one result's proof. |
| workspace_get_source_sliceC | Return bounded source text around one span, result, or proof. |
| workspace_get_result_reading_pathB | Return deterministic local reading paths for one result. |
| load_paperA | Load a local LaTeX paper and build its theorem graph. |
| load_arxiv_paperC | Download an arXiv source project and build its theorem graph. |
| load_arxiv_requestB | Validate a raw arXiv request, then load it only if unambiguous. |
| list_theoremsC | List theorem-like environments in the currently loaded paper. |
| get_theoremB | Return the full text and metadata for one theorem-like node. |
| get_dependenciesC | Return theorem-like nodes referenced by the given theorem. |
| get_dependency_diagnosticsB | Explain how dependencies were extracted for one theorem-like node. |
| where_usedB | Return theorem-like nodes that reference the given theorem. |
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 31 tools
Many tools have overlapping or near-identical functionality (e.g., workspace_add_local_paper vs load_paper, workspace_get_dependencies vs get_dependencies), making it difficult to choose the correct one.
Naming is inconsistent: some tools use the workspace_ prefix, others don't; verbs vary between add, load, list, get, and where_used, and there are duplicate concepts with different names.
31 tools is far beyond the typical well-scoped range, and the redundancy inflates the count unnecessarily, making the surface overwhelming and hard to navigate.
The tool set covers many reading and retrieval operations but lacks basic update/delete functionality, and the presence of duplicate operations suggests incomplete consolidation rather than comprehensive coverage.