terminologia — Claude Code MCP server: what it does, how to install
Connects your assistant to health terminologies via FHIR. Helps look up and validate codes across systems like CID-10 and TUSS.
claude mcp add --env TERMINOLOGIA_KEY=<TERMINOLOGIA_KEY> --env TERMINOLOGIA_URL=<TERMINOLOGIA_URL> --transport stdio terminologia -- uvx terminologiaWhat terminologia does
This tool connects your coding assistant to health nomenclature datasets via the Voa Health FHIR service. It exposes lookup and code verification tools across registries like CID-10, TUSS, and SIGTAP, along with LOINC.
Requests go to https://terminologia.voa.health/api/v1/fhir by default. Without a valid TERMINOLOGIA_KEY credential, every query fails. You can point the client to another endpoint using TERMINOLOGIA_URL.
What it helps with
- look up diagnosis codes in ICD-10 or ICPC-2
- validate medical billing codes in TUSS and SIGTAP
- translate codes across healthcare classification systems
- search health establishments registered in CNES
Example prompts for the agent
- Look up the ICD-10 code for chest pain
- Validate code 10101012 against the TUSS terminology system
- Search for clinics matching hospital das clinicas in CNES
How to install terminologia
Platform CLI
claude mcp add --env TERMINOLOGIA_KEY=<TERMINOLOGIA_KEY> --env TERMINOLOGIA_URL=<TERMINOLOGIA_URL> --transport stdio terminologia -- uvx terminologiaReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from terminologia <command>
Platform CLI
codex mcp add terminologia --env TERMINOLOGIA_KEY=<TERMINOLOGIA_KEY> --env TERMINOLOGIA_URL=<TERMINOLOGIA_URL> -- uvx terminologiaReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from terminologia <command>
Config file
{
"mcpServers": {
"terminologia": {
"command": "uvx",
"args": [
"terminologia"
],
"env": {
"TERMINOLOGIA_KEY": "<TERMINOLOGIA_KEY>",
"TERMINOLOGIA_URL": "<TERMINOLOGIA_URL>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from terminologia <command>
Config file
{
"servers": {
"terminologia": {
"type": "stdio",
"command": "uvx",
"args": [
"terminologia"
],
"env": {
"TERMINOLOGIA_KEY": "<TERMINOLOGIA_KEY>",
"TERMINOLOGIA_URL": "<TERMINOLOGIA_URL>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from terminologia <command>
Platform CLI
gemini mcp add -e TERMINOLOGIA_KEY=<TERMINOLOGIA_KEY> -e TERMINOLOGIA_URL=<TERMINOLOGIA_URL> terminologia uvx terminologiaReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from terminologia <command>
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about terminologia
How to install terminologia in Claude Code?
Run claude mcp add terminologia -e TERMINOLOGIA_KEY=<TERMINOLOGIA_KEY> -- uvx terminologia. Replace the placeholder with your actual access token.
What does the terminologia MCP server do?
It gives LLMs tools to query, validate, and translate medical codes across standards such as ICD-10, TUSS, TISS, and LOINC using FHIR endpoints.
Which credentials does the server require?
It requires a TERMINOLOGIA_KEY starting with sk_voa_, or an existing sk_tiss_ token configured with the terminology:read scope.
