Paper RAG MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAPER_RAG_PORT | No | Changes the port for Streamable HTTP mode. The HTTP URL is http://127.0.0.1:8765/mcp by default. | 8765 |
| PAPER_RAG_CONFIG | No | Selects a different configuration file. The default configuration is ~/.config/paper-rag/config.json. |
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 |
|---|---|
| list_papersA | Find active papers by title substring, exact DOI or paper ID. Empty query lists up to 50. Use IDs to scope search. No model call. |
| searchA | Retrieve source-first scientific evidence. Use faithful English scientific terms for Chinese questions; do not insert assumed answers. Optional paper_ids limits scope (maximum 10). Returns exact source spans, PDF pages, section headings, and result IDs for fetch. No answer generation. |
| fetchA | Read the original parent section for a search result ID, with hash validation and page provenance. Follow next_offset to read a long section. Never infer ownership from terminology alone. IDs must come from search; no arbitrary file access. |
| evidence_checklistB | Start scientific questions with an explicit evidence checklist. Add question-specific requirements; later submit every field to audit_answer. No scientific completeness guarantee. |
| audit_answerA | Before final answer, audit each checklist field. Each item: field, status (supported/missing/not_applicable), statement, reason for missing/not_applicable, citations=[{id: search result ID, quote: exact original text, offset: fetch offset}]. Checks source hashes, literal anchors and field accounting, NOT semantic entailment. Explicitly disclose missing evidence and unverified attribution. |
| citation_networkA | Read a configured frozen citation snapshot by library paper_id or OpenAlex W ID. Modes: references, citing, relations (shared references/co-citers and normalized similarities). Follow next_offset. Coverage is sampled, not exhaustive. No live expansion. |
| source_pageA | Read a 1-based ORIGINAL PDF page after source hash validation, optionally return its image. Use for table column alignment, footnotes, figures, formulas and missing experimental conditions. Does not fetch external supplements or certify interpretation. |
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 7 tools
Each tool has a clearly distinct role: listing papers, evidence search, section fetch, checklist creation, answer audit, citation graph lookup, and original page inspection. The main possible overlaps—search vs. fetch and fetch vs. source_page—are explicitly differentiated by result-ID scoping and page-level provenance. An agent can reliably select the right tool for each step.
Names are all snake_case and readable, but they mix bare verbs (search, fetch) with noun phrases (evidence_checklist, audit_answer, citation_network, source_page) and one verb_noun form (list_papers). The conventions are understandable but not predictably patterned across the set.
Seven tools is well-scoped for a retrieval-and-audit workflow over a paper corpus. Each tool maps to a distinct stage—discovery, search, reading, checklist, audit, citation exploration, and page inspection—without obvious redundancy.
The surface covers the core evidence workflow from paper discovery through source reading, citation exploration, and answer auditing. Minor gaps exist around library/ingestion operations or richer paper metadata retrieval, but these may be intentionally out of scope for a read-only RAG server.