Unofficial UniProt MCP Server

Created By
Augmented-Naturea year ago
A comprehensive Model Context Protocol (MCP) server providing advanced access to the UniProt protein database.
Overview

What is the Unofficial UniProt MCP Server?

The Unofficial UniProt MCP Server is a comprehensive Model Context Protocol (MCP) server that provides advanced access to the UniProt protein database, enabling sophisticated protein research and analysis.

How to use the Unofficial UniProt MCP Server?

To use the server, clone the repository, install dependencies, and run the server. You can also integrate it with MCP clients for seamless access to protein data.

Key features of the Unofficial UniProt MCP Server?

  • 26 specialized bioinformatics tools for protein analysis, comparative genomics, and structural biology.
  • Advanced search capabilities including batch processing and complex queries.
  • Integration with external databases and literature references.

Use cases of the Unofficial UniProt MCP Server?

  1. Conducting detailed protein analysis for research.
  2. Performing comparative genomics and evolutionary studies.
  3. Analyzing protein structures and functions for drug discovery.

FAQ from the Unofficial UniProt MCP Server?

  • Can I access all protein data through this server?

Yes, the server provides comprehensive access to the UniProt protein database.

  • Is there a cost to use the Unofficial UniProt MCP Server?

No, it is free to use.

  • What programming languages are supported?

The server is developed using JavaScript and requires Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Augmented-Nature
Star
0
Language
JavaScript
License
MIT 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