UbiMCP Overview
UbiMCP is a single Model Context Protocol endpoint that gives an LLM client unified access to the enabled UniBio Intelligence biomedical data sources. Instead of integrating separate APIs by hand, you connect one MCP server and the LLM can answer questions that span targets, diseases, drugs, gene annotation, expression, FDA data, and antibody registry records.
What it covers
| Domain | Sources |
|---|---|
| Target and disease knowledge | Open Targets, MyDisease |
| Genomics | NCBI Datasets, MyGene |
| Gene expression | GTEx |
| Chemistry and drugs | MyChem |
| Clinical and regulatory | openFDA |
| Protein and antibody records | Antibody Registry |
The full catalog with per-server descriptions is on the Servers page.
How LLMs use it
UbiMCP exposes a small, fixed set of discovery and execution tools. The LLM finds the right underlying tool through a search-plan-execute pattern rather than seeing every underlying function at once. This keeps context usage low and routing fast.
The six core tools are:
| Tool | Purpose |
|---|---|
search_tools(query) | Semantic search across every tool in every enabled server |
discover_servers(scope, category) | List enabled servers, usually with scope="ubi-bio" |
discover_tools(server) | List tools belonging to one server |
get_tool_schema(tool_name) | Get the JSON schema for one tool's parameters |
execute_tool(server, tool_name, params) | Call any tool on any enabled server |
health_check() | Server status |
See Discovery Tools for examples.
Connection options
UbiMCP is available through the hosted HTTP endpoint:
https://mcp.unibiointelligence.com/mcp
Client-specific setup walkthroughs:
License and use
UbiMCP wraps public biomedical databases. You are responsible for honoring each underlying source's terms of use. Outputs are intended for research and are not a medical device.