Snowstorm MCP Server logo

Snowstorm MCP Server

Unclaimed

by IHTSDO

An MCP server for querying SNOMED CT clinical terminology via Snowstorm and Snowstorm Lite backends.

Install

$uv run --project /path/to/snowstorm-mcp-server snowstorm-mcp-server --transport stdio

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
mcp-serversnomed-ct

More in Developer Tools

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

15 of 15 tools

Documented tools (15)

From project documentation. A server handshake does not verify each tool’s description or behavior.

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Snowstorm MCP Server

How do I connect Snowstorm MCP Server to Claude?
The listing records `uv run --project /path/to/snowstorm-mcp-server snowstorm-mcp-server --transport stdio` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop as compatible clients.
Is Snowstorm MCP Server free?
The listed licence is Apache-2.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Snowstorm MCP Server do?
Snowstorm MCP Server documents 15 tools to the agent, including fhir_metadata, list_terminologies, server_capabilities. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.