4,000+ servers built on vurb.ts
Vinkius

EBI Proteins API MCP Server for Claude DesktopGive Claude Desktop instant access to 16 tools to Get Antigen, Get Coordinates, Get Genecentric, and more

MCP Inspector GDPR Free for Subscribers

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this MCP Server for Claude Desktop

The EBI Proteins API MCP Server for Claude Desktop is a standout in the The Unthinkable category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Classic Setup·json
{
  "mcpServers": {
    "ebi-proteins-api": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install EBI Proteins API and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
EBI Proteins API
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About EBI Proteins API MCP Server

Connect to the EMBL-EBI Proteins API and access comprehensive protein biology data from one of the world's leading bioinformatics institutes.

Claude Desktop is the definitive way to connect EBI Proteins API to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 16 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Protein Retrieval — Fetch complete protein entries by UniProt accession with names, organisms, gene information, sequences, and cross-references
  • Sequence Features — Retrieve annotated domains, binding sites, active sites, signal peptides, transmembrane regions, and disulfide bonds for any protein
  • Genetic Variants — Access curated variants from UniProtKB aggregated with large-scale studies including ClinVar, gnomAD, 1000 Genomes, COSMIC, and TOPMed
  • Proteomics & PTMs — Query mass-spectrometry peptide evidence and post-translational modifications from PeptideAtlas, MaxQB, EPD, and ProteomicsDB
  • Mutagenesis — Explore curated mutagenesis experiments with detailed phenotypic effect descriptions
  • Proteomes & Taxonomy — Search reference proteomes and navigate the taxonomy tree by ID or organism name
  • Genome Coordinates — Map proteins to genome positions on GRCh38/GRCh37 with Ensembl gene, transcript, and translation IDs

The EBI Proteins API MCP Server exposes 16 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 EBI Proteins API tools available for Claude Desktop

When Claude Desktop connects to EBI Proteins API through Vinkius, your AI agent gets direct access to every tool listed below — spanning proteins, uniprot, bioinformatics, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get antigen on EBI Proteins API

These are peptide regions used for antibody generation, indicating experimentally validated protein expression targets. Useful for immunology and antibody-based research. Get antigen sequences from Human Protein Atlas

get

Get coordinates on EBI Proteins API

Returns Ensembl gene, transcript, and translation IDs along with chromosome, start/end positions, and strand information. Essential for bridging protein annotations with genomic data. Get genome coordinate mappings for a protein

get

Get genecentric on EBI Proteins API

Shows canonical protein and related protein count for each gene. Use with a UniProt Proteome ID (e.g. UP000005640). Get the gene-centric view of a proteome

get

Get mutagenesis on EBI Proteins API

Each entry includes the wild-type and mutant residues, position, and a description of the functional impact. Critical for understanding structure-function relationships. Get mutagenesis experiments and phenotypic effects

get

Get protein on EBI Proteins API

Use a UniProt accession such as P12345, Q9Y6K9, or P53_HUMAN. Retrieve a full protein entry by UniProt accession

get

Get protein features on EBI Proteins API

Features include domains, binding sites, active sites, signal peptides, transmembrane regions, disulfide bonds, glycosylation sites, and more. Each feature has start/end positions and evidence counts. Get sequence feature annotations for a protein

get

Get proteome on EBI Proteins API

Returns taxonomy, protein count, gene count, reference status, and component information. Use IDs like UP000005640 for human proteome or UP000000589 for mouse. Get a specific proteome by UniProt Proteome ID

get

Get proteomics on EBI Proteins API

Shows which peptides have been experimentally detected and whether they are unique to this protein. Essential for validating protein expression. Get mass-spectrometry proteomics data for a protein

get

Get proteomics ptm on EBI Proteins API

Provides residue-level PTM positions with evidence counts. Get post-translational modifications from mass-spec data

get

Get taxonomy on EBI Proteins API

Returns scientific name, common name, rank, lineage, parent, and children nodes. Use IDs like 9606 for human, 10090 for mouse, 562 for E. coli. Get taxonomy node details by NCBI taxon ID

get

Get variation on EBI Proteins API

Each variant includes wild-type and mutant residues, clinical significance, consequence type (e.g. missense, nonsense), and cross-references. Critical for clinical genomics and variant interpretation. Get genetic variants for a protein from multiple sources

search

Search features by type on EBI Proteins API

Valid types include: DOMAIN, BINDING, ACTIVE_SITE, SIGNAL, TRANSMEM, DISULFID, CARBOHYD, MOD_RES, VARIANT, MUTAGEN, REGION, MOTIF, SITE, REPEAT, COILED, COMPBIAS, HELIX, STRAND, TURN. Search features by type across proteins

search

Search proteins on EBI Proteins API

You can combine gene name (e.g. TP53), organism (e.g. human, 9606), keyword (e.g. kinase), or accession. Returns a summarized list of matching proteins with names, organisms, and sequence lengths. Search proteins by gene name, organism, or keyword

search

Search proteomes on EBI Proteins API

Returns proteome IDs, taxonomy, protein counts, gene counts, and reference proteome status. Use queries like "homo sapiens", "escherichia coli", "arabidopsis". Search proteomes by organism name

search

Search taxonomy on EBI Proteins API

Returns matching taxonomy entries with scientific names, common names, taxon IDs, and ranks. Useful for finding the correct taxon ID before querying proteins or proteomes for a specific organism. Search taxonomy by organism name

search

Search variation on EBI Proteins API

g. large_scale_study, uniprot, mixed), consequence type (e.g. missense, stop gained), and wild-type residue. Use this to find clinically relevant variants across the proteome. Search variants by consequence type, source, or residue

Connect EBI Proteins API to Claude Desktop via MCP

Follow these steps to wire EBI Proteins API into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using EBI Proteins API

Look for the 🔌 icon in the chat. your 16 tools are now available

Why Use Claude Desktop with the EBI Proteins API MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with EBI Proteins API through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

EBI Proteins API + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the EBI Proteins API MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for EBI Proteins API in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with EBI Proteins API immediately.

01

"Get all known genetic variants for the TP53 tumor suppressor protein."

02

"Show me the domain architecture and binding sites of the EGFR protein."

03

"Map the BRCA1 protein to its genome coordinates on GRCh38."

Troubleshooting EBI Proteins API MCP Server with Claude Desktop

Common issues when connecting EBI Proteins API to Claude Desktop through Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

EBI Proteins API + Claude Desktop FAQ

Common questions about integrating EBI Proteins API MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Explore More MCP Servers

View all →