ArXivLens MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub token to increase API rate limits (optional, default no token) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_arxivB | Search papers on arXiv in real time. |
| get_paper_detailsA | Retrieve full metadata and abstract for a specific arXiv ID. |
| find_code_repositoriesA | Discover open-source GitHub repositories implementing or referencing an arXiv paper. |
| generate_research_briefB | Synthesize an executive research brief for a paper, including problem statement, methodology, key findings, and matching code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| literature_review | Systematic literature review prompt template guiding an LLM to scout papers and synthesize findings. |
| paper_critique | Critical evaluation prompt guiding an LLM to assess methodology, rigor, and limitations of a paper. |
| reproducibility_audit | Reproducibility and open-science audit prompt for an academic paper. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_categories_resource | List of all supported academic research categories and domains. |
TDQS
Scored across 4 tools
Each tool targets a distinct stage of the research workflow: searching, retrieving metadata, finding code, and generating a synthesis. There is no meaningful overlap between tool purposes.
All tool names follow a consistent verb_noun pattern with clear, descriptive verbs: search, get, find, generate. The naming convention is uniform throughout.
Four tools is well-scoped for an arXiv research assistant: search, detail retrieval, code discovery, and brief generation. Each tool earns its place and the set is neither bloated nor too thin.
The surface covers the full research journey from discovery to synthesis, including practical follow-up like finding code repositories. No obvious dead ends or missing lifecycle steps are apparent for this domain.