Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-opentargets search for drugs related to rheumatoid arthritis"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Open Targets MCP — disease/target/drug knowledge graph that integrates genetic, genomic, transcriptomic, and chemistry evidence. Keyless GraphQL public endpoint.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
target(ensembl_id) — target (gene) profile
disease(efo_id) — disease profile
drug(chembl_id) — drug profile
search(query, entity?, size?) — platform search
target_associations(ensembl_id, size?) — top diseases for a target
disease_associations(efo_id, size?) — top targets for a disease
target_known_drugs(ensembl_id, size?) — clinically tested drugs for a target
Related MCP server: mcp-chembl
https://api.platform.opentargets.org/api/v4/graphql
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"opentargets": {
"url": "https://gateway.pipeworx.io/opentargets/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/opentargets/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Opentargets data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Link compounds to protein targets, rank bioactivity, and look up drug mechanisms and indications.
Knowledge graph ingestion, entity search, ontology analysis, and CoSync scoring.
Knowledge graph ingestion, entity search, ontology analysis, and CoPass scoring.
Search biomedical papers, inspect publication records, and traverse citation or semantic graphs.
