arxiv-mcp-server MCP工具

Optional dependencies

Choose the install variant that matches the features you need:

```bash

Install

The default install is uvx arxiv-mcp-server. Command-based integrations need uv, which provides uvx. No repository clone or Python environment setup is required.

uvx arxiv-mcp-server

Add this stdio configuration to clients that accept the mcpServers JSON shape, such as Claude Desktop and Kiro. Other clients may use a top-level servers object, TOML, or their own settings UI; consult the client's MCP documentation.

{
  "mcpServers": {
    "arxiv": {
      "type": "stdio",
      "command": "uvx",
      "args": ["arxiv-mcp-server"]
    }
  }
}

The default paper directory is ~/.arxiv-mcp-server/papers. To choose another directory, append "--storage-path", "/absolute/path/to/papers" to args.

The supported package is published on PyPI as arxiv-mcp-server==0.7.2. An unrelated npm package uses the same name, so do not install this server with npm, pnpm, or npx arxiv-mcp-server.

Listed on the official MCP registry, latest 0.7.2.

If an existing installation is missing newer tools

uvx reuses cached tool environments. Force it to resolve the current PyPI release with a supported interpreter, then restart your MCP client:

uvx --python 3.11 --refresh-package arxiv-mcp-server arxiv-mcp-server

If your client still launches an older environment, add "--python", "3.11" before "arxiv-mcp-server" in its args array.

Persistent command install

To place arxiv-mcp-server on your PATH instead of launching it through uvx:

uv tool install arxiv-mcp-server

If the command is not immediately available, run uv tool update-shell and restart the terminal. Afterward, use "command": "arxiv-mcp-server" and omit the package name from args.

search_papers query guide

Tool schemas stay short on purpose. Use this section (not the always-loaded MCP description) for query tutorials, category catalogs, and workflow examples.

Query construction

• Use quoted phrases for exact matches: "multi-agent systems", "neural networks"
• Combine related concepts with OR: "AI agents" OR "software agents"
• Field-specific searches: ti:"exact title phrase", au:"author name", abs:"keyword", cat:cs.LG
• Exclude with ANDNOT: "machine learning" ANDNOT "survey"
• Prefer 2–4 core concepts over long keyword lists

Advanced patterns

• Field + phrase: ti:"transformer architecture"
• Multiple fields: au:"Smith" AND ti:"quantum"
• Exclusions: "deep learning" ANDNOT ("survey" OR "review")
• Broad + narrow: "artificial intelligence" AND (robotics OR "computer vision")

Category filtering (recommended for relevance)

Computer Science: cs.AI (AI), cs.LG (ML), cs.CL (NLP), cs.CV (vision), cs.MA (multi-agent), cs.RO (robotics), cs.NE (neural/evolutionary), cs.IR (IR), cs.HC (HCI), cs.CR (security), cs.DB (databases)

Statistics & Math: stat.ML, stat.AP, math.OC, math.ST

Physics & other: quant-ph, eess.SP, eess.AS, physics.data-an

Effective examples

• ti:"reinforcement learning" with categories: ["cs.LG", "cs.AI"]
• au:"Hinton" AND "deep learning" with categories: ["cs.LG"]
• "multi-agent" ANDNOT "survey" with categories: ["cs.MA"]
• abs:"transformer" AND ti:"attention" with categories: ["cs.CL"]

Dates and sorting

• Dates use YYYY-MM-DD (date_from / date_to)
• Default sort_by is relevance; use date for newest-first monitoring
• Foundational work: date_to: "2010-12-31" with title/abstract field searches

Result size, abstracts, and pagination

• Default max_results is 5 (cap 50). Pass an explicit value for larger pages.
• abstract_mode: snippet (default, ~280 chars, marked … [truncated] when cut), full (complete abstract), or none (omit abstracts). Other metadata (title, authors, categories, dates, URLs) is always returned.
• Responses report total_results (corpus hits), returned, has_more, start, next_start, and abstract_mode
• Pass start=next_start with the same abstract_mode for the next page
• arXiv enforces ~3 seconds between requests (handled server-side); on rate-limit errors wait ~60s

Configuration

Environment variable names are case-insensitive through Pydantic settings. --storage-path is a command-line option rather than an environment setting.

Plugin manifests

The same MCP server and research skill are packaged for both major plugin systems:

</details>

VS Code and Kiro

For the richer Kiro Power integration, open the Powers panel, choose Add Custom Power → Import power from GitHub, and enter:

https://github.com/blazickjp/arxiv-mcp-server

The Power installs the MCP connection from mcp.json and adds focused arXiv research guidance. Kiro users who prefer manual configuration can place the generic configuration above in .kiro/settings/mcp.json for one workspace or ~/.kiro/settings/mcp.json for all workspaces.