Vertical Search

Created By
daheepka year ago
Overview

What is the arXiv Research Assistant MCP Server?

The arXiv Research Assistant MCP Server is a Model Context Protocol (MCP) server designed to interact with the extensive arXiv.org paper database, enabling efficient searching, exploring, and comparing of research papers.

How to use the arXiv Research Assistant MCP Server?

To use the server, install it via Smithery or PyPI, run the server locally, and configure it with compatible clients like Claude AI by adding the necessary JSON configuration to their MCP settings.

Key features of the arXiv Research Assistant MCP Server?

  • Keyword-based Paper Search: Search papers by keywords with sorting options.
  • Latest Papers by Category: Fetch recent papers in specified arXiv categories.
  • Paper Details Lookup: Retrieve detailed metadata using a paper's arXiv ID.
  • Author-based Paper Search: List papers published by specific authors.
  • Trend Analysis: Overview of trending keywords/topics in recent papers (experimental).
  • Summarization Prompt Generator: Generate prompts for summarizing papers.
  • Comparison Prompt Generator: Create structured prompts for comparing two papers.

Use cases of the arXiv Research Assistant MCP Server?

  1. Researchers can quickly find relevant papers in their field of study.
  2. Students can explore recent advancements in specific categories.
  3. Academics can compare research outputs from different authors.

FAQ from the arXiv Research Assistant MCP Server?

  • Can I search for papers in any category?

    Yes, you can specify any arXiv category code to fetch recent papers.

  • Is the server easy to set up?

    Yes, installation can be done via Smithery or PyPI with simple commands.

  • What programming language is used?

    The server is built using Python and the FastMCP framework.

Server Config

{
  "mcpServers": {
    "arXivPaper": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "arxiv-paper-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
daheepk
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago