DROMA MCP Server

A Model Context Protocol (MCP) server for DROMA (Drug Response Omics association MAp) - enabling natural language interactions with drug-omics association analysis. Exposed over MCP by the droma mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• 🔗 Natural Language Interface — Ask questions about drug-omics associations in plain English
• 📊 Dataset Management — Load and manage DROMA datasets (CCLE, gCSI, etc.) in memory
• 📈 Data Loading & Normalization — Load molecular profiles and treatment response data with automatic z-score normalization
• 🗂️ Multi-Project Support — Seamlessly work with data across multiple research projects
• 💾 Smart Caching — Efficient data caching with metadata tracking for faster access
• 📤 Data Export — Export analysis results to various formats (CSV, Excel, JSON)

Its toolset

Everything the assistant can do here goes through one of these:

• run — Start the MCP server
• test — Test configuration and dependencies
• validate — Validate complete setup
• export-config — Export MCP client configuration
• Prerequisites — The Prerequisites tool exposed by this server

Configuration

You will need one environment variable: DROMA_DB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Python 3.10+ - R 4.0+ with DROMA.Set and DROMA.R packages - DROMA SQLite database - FastMCP 2.13+ (automatically installed)

Adding it to your client

The server ships on PyPI as droma-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. DROMA MCP's toolset — run, test, validate and 2 more — is a fair guide to whether it matches your workflow. It is maintained by mugpeng; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the droma mcp mcp server does with a few real requests.