Icf MCP logo

Icf MCP

Queries WHO ICF codes, hierarchy, qualifiers, and assessment instruments through one MCP tool over streamable HTTP.

Install Icf MCP

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp-icf.medseal.app/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

The icf-mcp MCP server exposes WHO International Classification of Functioning, Disability and Health data through a streamable HTTP MCP endpoint. Its single `icf` tool dispatches actions for code lookup, keyword search, hierarchy navigation, qualifier handling, functional profiles, and 11 assessment instruments. Code and hierarchy operations use WHO ICD-API credentials, while instrument and qualifier logic works without them. Reach for it when an agent needs structured ICF classifications, code validation, or instrument scoring.

Use cases

  • Look up WHO ICF codes by identifier
  • Search ICF categories by health or functioning terms
  • Validate and parse qualified ICF codes
  • Score standardized assessment instrument responses
  • Build functional profiles from multiple codes

Key features

  • WHO ICF code lookup and keyword search
  • Hierarchy browsing and parent-child navigation
  • Qualifier parsing and validation
  • Functional profile construction
  • Scoring for 11 clinical assessment instruments
  • Streamable HTTP deployment on Cloudflare Workers

Tools1

What Icf MCP lets your agent do. Expand a tool for its parameters.

Verified live~391 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 34d

What it can do

From the 1 tool this server returned when we ran it.

Read-only tools · 1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
Last commit3mo agoMost recent push to the default branch.
Tools exposed1Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Icf MCP works

What icf-mcp MCP server does

The icf-mcp MCP server provides agent access to the WHO International Classification of Functioning, Disability and Health (ICF). ICF complements diagnosis-oriented classifications by describing functioning across body functions, body structures, activities and participation, and environmental factors.

The service supports looking up individual codes such as b280 or d450, searching by terms, browsing categories, and moving through the classification hierarchy. It can also construct a functional profile from multiple codes. Qualifier operations cover component-specific references, validation, and parsing of qualified codes such as d450.23, s730.312, and e120+3.

How it works

A single icf MCP tool accepts an action and related parameters. The available actions cover classification data, qualifiers, clinical instruments, metadata, and a raw WHO API escape valve. This action-dispatch design keeps the tool surface compact while exposing 19 operations.

The deployed endpoint is https://mcp-icf.medseal.app/mcp. The repository also supports running the Worker locally or deploying it to a Cloudflare account. The MCP protocol endpoint uses streamable HTTP; / and /health provide health or server information.

Classification and hierarchy actions query the WHO ICD-API, which requires a WHO ICD-API client ID and client secret. Qualifier and instrument operations are implemented as local logic and do not require WHO API credentials. The server runs on Cloudflare Workers, providing the deployment model described by the repository.

Setup and configuration

To run the icf-mcp MCP server from source, use Node.js 18 or newer, npm, a Cloudflare account with Workers enabled, and free WHO ICD-API credentials. Clone the repository, install dependencies with npm install, and copy .dev.vars.example to .dev.vars for local configuration.

Set WHO_CLIENT_ID and WHO_CLIENT_SECRET in the local variables file. For a deployed Worker, store the same values as Wrangler secrets:

  • wrangler secret put WHO_CLIENT_ID
  • wrangler secret put WHO_CLIENT_SECRET

Run npm run dev for a local server at http://localhost:8787, npm test for the included tests, and npm run deploy to deploy. The repository also documents a production Wrangler environment and a custom domain configuration. Claude Desktop can connect by adding the MCP URL to its configuration; a self-hosted Worker can use its own /mcp URL.

Tools and capabilities

The icf tool supports these main groups of operations:

  • Code and hierarchy: lookup, search, browse, children, parent, siblings, chain, and profile.
  • Qualifiers: qualifier, validate, and parse.
  • Instruments: instruments, instrument, score, suggest, and mapping.
  • Metadata: overview, api, and help.

The instrument catalog includes GAD-7, PHQ-9, RADAI-5, SLEDAI-2K, WHODAS 2.0, HAQ-DI, PROMIS-10, CAT, ODI, NRS Pain, and Short FES-I. Instrument actions can list or inspect instruments, score responses, suggest an instrument for a condition, code, or domain, and show ICF mappings.

Limitations and notes

The icf-mcp MCP server depends on WHO ICD-API credentials for code and hierarchy requests. Tests described in the repository focus on instrument scoring and qualifier parsing, so those tests do not require WHO credentials. The server covers ICF functionality described by its action interface; the README identifies ICD-11 only as another classification available through the underlying WHO API, not as a separate set of server tools.

The repository is licensed under MIT. The related Python project is listed separately for Claude Desktop use, while this project is the Cloudflare Workers implementation.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Icf MCP

icf-mcp is an MCP server that connects AI agents to the WHO ICF classification through the WHO ICD-API. Its main tools are exposed through one action-based `icf` tool for code lookup, search, hierarchy browsing, qualifier parsing and validation, functional profiles, and scoring or mapping 11 standardized assessment instruments.

Clone the repository, install dependencies with Node.js 18+ and npm, then configure WHO credentials in `.dev.vars` for local use. Run `npm run dev` to start the local Worker, or `npm run deploy` to deploy it to Cloudflare Workers.

Code and hierarchy actions require WHO ICD-API credentials stored as `WHO_CLIENT_ID` and `WHO_CLIENT_SECRET`. Qualifier and instrument actions do not require WHO API credentials because they use local logic.

Yes, icf-mcp works with Claude Desktop through its streamable HTTP MCP endpoint. Add `https://mcp-icf.medseal.app/mcp` to the `mcpServers` configuration, or provide the `/mcp` URL of a Worker you deploy yourself.

icf-mcp supports 11 instruments: GAD-7, PHQ-9, RADAI-5, SLEDAI-2K, WHODAS 2.0, HAQ-DI, PROMIS-10, CAT, ODI, NRS Pain, and Short FES-I. It can list instruments, inspect specifications, score responses, suggest instruments, and show ICF mappings.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewIcf MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/icf-mcp?style=directory)](https://allmcps.com/mcp/icf-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/icf-mcp"><img src="https://allmcps.com/api/badge/icf-mcp?style=directory" alt="Icf MCP on AllMCPs" /></a>