Unofficial Ensembl MCP Server

Created By
Augmented-Naturea year ago
A comprehensive Model Context Protocol (MCP) server that provides access to the Ensembl REST API for genomic data, comparative genomics, and biological annotations.
Overview

What is Ensembl MCP Server?

The Ensembl MCP Server is an unofficial Model Context Protocol server that provides access to the Ensembl REST API for genomic data, comparative genomics, and biological annotations.

How to use Ensembl MCP Server?

To use the Ensembl MCP Server, clone the repository, install dependencies, build the server, and configure it with Claude Desktop to access genomic data through natural language queries.

Key features of Ensembl MCP Server?

  • Gene and transcript information retrieval
  • Genomic sequence extraction and translation
  • Comparative genomics tools for homolog detection and phylogenetic analysis
  • Variant data retrieval and consequence prediction
  • Access to regulatory features and annotations
  • Batch processing capabilities for multiple queries

Use cases of Ensembl MCP Server?

  1. Researchers can look up gene information and sequences for their studies.
  2. Bioinformaticians can analyze genetic variants and their effects.
  3. Educators can use the server to demonstrate genomic concepts in teaching.

FAQ from Ensembl MCP Server?

  • What types of data can I access?

You can access genomic sequences, gene annotations, variant data, and regulatory features across multiple species.

  • Is there a limit on API requests?

Yes, the server respects Ensembl's rate limiting guidelines, allowing a maximum of 15 requests per second.

  • Can I contribute to the project?

Yes! Contributions are welcome, and you can help improve the server by ensuring TypeScript compliance and updating documentation.

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
Crevio

2 days ago