Biorxiv

Created By
JackKuo666a year ago
Overview

What is bioRxiv MCP Server?

The bioRxiv MCP Server is a tool that enables AI assistants to search and access bioRxiv papers through a simple Model Context Protocol (MCP) interface, facilitating access to biology preprints and their metadata.

How to use bioRxiv MCP Server?

To use the bioRxiv MCP Server, clone the repository from GitHub, install the required dependencies, and start the server using Python. You can then query the server for papers or metadata using an AI assistant.

Key features of bioRxiv MCP Server?

  • 🔎 Paper Search: Query bioRxiv papers with keywords or advanced search options.
  • 🚀 Efficient Retrieval: Fast access to paper metadata.
  • 📊 Metadata Access: Retrieve detailed metadata for specific papers.
  • 📄 Paper Access: Download and read paper content.
  • 🗃️ Local Storage: Save papers locally for faster access.
  • 📝 Research Prompts: Specialized prompts for paper analysis.

Use cases of bioRxiv MCP Server?

  1. Searching for recent biology research papers.
  2. Accessing detailed metadata for specific studies.
  3. Facilitating research analysis in biological sciences.

FAQ from bioRxiv MCP Server?

  • Can I search for papers on any biology topic?

Yes! You can search for papers using keywords related to any biology topic.

  • Is there a limit to the number of papers I can access?

No, you can access as many papers as available in the bioRxiv repository.

  • What are the prerequisites for using this server?

You need Python 3.10+ and the FastMCP library installed.

Server Config

{
  "mcpServers": {
    "biorxiv": {
      "command": "bash",
      "args": [
        "-c",
        "source /home/YOUR/PATH/mcp-server-bioRxiv/.venv/bin/activate && python /home/YOUR/PATH/mcp-server-bioRxiv/biorxiv_server.py"
      ],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JackKuo666
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)

a day ago