🧬 Ensembl API MCP Server

Created By
effieklimia year ago
A full-featured Model Context Protocol (MCP) server that exposes Ensembl’s REST API. Built using the TypeScript MCP SDK
Overview

what is Ensembl MCP Server?

Ensembl MCP Server is a Model Context Protocol (MCP) server that provides access to the Ensembl genomics database, enabling AI assistants to query genomic data, gene information, sequences, variants, and more.

how to use Ensembl MCP Server?

To use the Ensembl MCP Server, clone the repository, install the dependencies using Bun, build the server, and start it. You can then connect it to an MCP-enabled LLM client to query genomic data.

key features of Ensembl MCP Server?

  • Gene Information retrieval by ID or symbol
  • Gene Search across species
  • Sequence Retrieval for genomic regions
  • Variant Data querying and annotations
  • Transcript Info access
  • Support for all Ensembl species
  • Cross-References to external databases
  • Built-in rate limiting to respect API limits

use cases of Ensembl MCP Server?

  1. Querying gene information for research purposes
  2. Searching for genetic variants in specific regions
  3. Retrieving DNA sequences for genomic analysis
  4. Accessing transcript details for gene studies
  5. Listing available species in Ensembl for comparative genomics

FAQ from Ensembl MCP Server?

  • Can I access all genomic data through this server?

Yes! The server provides access to a wide range of genomic data from the Ensembl database.

  • Is there a limit on the number of requests I can make?

Yes, the server has built-in rate limiting to respect Ensembl's API limits, allowing a maximum of 10 requests per second.

  • Do I need an API key to use the Ensembl MCP Server?

No, the Ensembl database is open access, so no API key is required.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
effieklimi
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