🧬 MCP PRIDE Archive Search Server

Created By
PRIDE-Archivea year ago
Model Context Protocol (MCP) PRIDE API Server implementation.
Overview

MCP PRIDE Archive Search is an API server that implements the Model Context Protocol (MCP) to facilitate programmatic access to the PRIDE Archive, a repository for proteomics data.

To use the server, clone the repository, install the dependencies, and start the server with your preferred connection type (http or stdio).

  • MCP Server powered by FastMCP
  • Search tool for querying datasets by various parameters
  • AI-friendly tools for biomedical research
  • Supports both http and stdio connection modes
  • Easily extendable with additional tools
  1. Searching for proteomics research data.
  2. Querying mass spectrometry datasets.
  3. Exploring biomedical datasets related to cancer.
  4. Finding specific or popular proteomics projects.
  • What is the purpose of this API server?

It allows AI models to interact with proteomics datasets programmatically.

  • How do I install the server?

Clone the repository and install dependencies using poetry or pip.

  • Can I use this server with any LLM?

Yes, it works with any LLM that supports the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PRIDE-Archive
Star
1
Language
Python
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