# OMOPHub MCP server

> Search, map and resolve medical codes across SNOMED CT, ICD-10, RxNorm and LOINC using OHDSI standardized vocabularies.

- Listing: https://mcp.tc/i/omophub
- Connect: use the server's own URL `https://mcp.omophub.com` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Databases & Backend](https://mcp.tc/c/databases)
- Vendor: OMOPHub
- Homepage: <https://omophub.com/>

## About

Connects to OMOPHub's hosted OHDSI ATHENA vocabularies. You can search concepts by keyword or natural language, look up codes, walk concept hierarchies, map between coding systems such as SNOMED CT, ICD-10-CM, RxNorm and LOINC, and resolve FHIR codings to OMOP standard concepts.

Runs as a hosted streamable HTTP endpoint at https://mcp.omophub.com. The endpoint answers without sign-in or an API key. The OMOPHub REST API and SDKs use an API key from the OMOPHub dashboard.

## What it can do

- Keyword and semantic search for OMOP concepts
- Look up concepts by ID or vocabulary code
- Navigate ancestors and descendants in hierarchies
- Map concepts across vocabularies
- Resolve FHIR codes and CodeableConcepts to OMOP
- Find similar concepts for phenotype concept sets
- List available vocabularies

## Tools (11)

- `search_concepts`: Keyword search for OMOP concepts by name, synonym or clinical term.
- `semantic_search`: Natural language concept search using neural embeddings, ranked by similarity.
- `find_similar_concepts`: Find concepts similar to a concept ID, name or query using semantic, lexical or hybrid matching.
- `get_concept`: Get details for an OMOP concept by its concept\_id.
- `get_concept_by_code`: Look up a concept by vocabulary ID and vocabulary-specific code.
- `explore_concept`: Get concept details, hierarchy and cross-vocabulary mappings in one call.
- `map_concept`: Find mappings from a source concept to equivalent concepts in other vocabularies.
- `get_hierarchy`: Navigate ancestors and descendants of a concept.
- `list_vocabularies`: List available vocabularies with concept counts and metadata.
- `fhir_resolve`: Resolve a FHIR system and code to an OMOP standard concept and CDM target table.
- `fhir_resolve_codeable_concept`: Resolve a FHIR CodeableConcept with multiple codings to the best OMOP match.

## Example prompts

- "Find the standard OMOP concept for acute kidney injury."
- "Map ICD-10-CM N17.9 to its SNOMED CT equivalent."
- "Build a concept set for type 2 diabetes including descendants."
- "Resolve FHIR code 2160-0 from http://loinc.org to an OMOP concept."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http omophub https://mcp.omophub.com
```

2. Start Claude Code and type `/mcp`. **omophub** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **OMOPHub** and paste this URL:

```url
https://mcp.omophub.com
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=OMOPHub&connectorUrl=https%3A%2F%2Fmcp.omophub.com>) (opens connector settings)

2. Check that the URL reads `https://mcp.omophub.com` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.omophub.com` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=omophub&config=eyJ1cmwiOiJodHRwczovL21jcC5vbW9waHViLmNvbSJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "omophub": {
      "url": "https://mcp.omophub.com"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=omophub&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.omophub.com%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"omophub","type":"http","url":"https://mcp.omophub.com"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "omophub": {
      "type": "http",
      "url": "https://mcp.omophub.com"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "omophub": {
      "serverUrl": "https://mcp.omophub.com"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add omophub --url https://mcp.omophub.com
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.omophub]
url = "https://mcp.omophub.com"
```

### Gemini CLI

```bash
gemini mcp add --transport http omophub https://mcp.omophub.com
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "omophub": {
      "type": "http",
      "url": "https://mcp.omophub.com"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.omophub.com`.

## Recent changes

- 2026-10-23 22:27 UTC: Tracking started: 11 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/omophub#history (Atom feed: https://mcp.tc/i/omophub/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.6.3
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-23
- Updated: 2026-10-23

---
Source: https://mcp.tc/i/omophub (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
