bioportal_mappings

Pack: bioportal · Endpoint: https://gateway.pipeworx.io/bioportal/mcp

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/bioportal_mappings for the schema, then POST the same URL with its arguments for the data.

Cross-ontology mappings for one class — the equivalent concepts in every other BioPortal ontology, with the mapping source (SAME_URI, LOOM, CUI, REST). AUTHORITATIVE for translating a code between terminologies, e.g. an NCIT concept to its SNOMEDCT, MESH and ICD10CM equivalents. Pass the ontology acronym and class IRI.

Parameters

Example call

Arguments

{
  "ontology": "NCIT",
  "class_id": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#C3224",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/bioportal/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"bioportal_mappings","arguments":{"ontology":"NCIT","class_id":"http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#C3224","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('bioportal_mappings', {
  "ontology": "NCIT",
  "class_id": "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl#C3224",
  "limit": 5
});

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "bioportal": {
      "url": "https://gateway.pipeworx.io/bioportal/mcp"
    }
  }
}

See Getting Started for client-specific install steps.