Skip to main content
Glama
README.md
# CME Conferences API and MCP server

Free, open data on **540 US CME conferences** (medical conferences 2026-11-17 to 2030-10-25) and **CE / CME requirements by state**, from [MedCE Hub](https://medcehub.com), the directory of continuing medical education conferences in the United States.

* **API docs (Swagger / OpenAPI):** https://medce-hub.github.io/cme-conferences-api/
* **Format:** [JSON:API 1.1](https://jsonapi.org/), static files, no API key
* **MCP server:** lets Claude, ChatGPT and other AI assistants search CME conferences and look up state CE requirements
* **Updated:** regularly. Last build 2026-11-18
* **License:** data CC BY 4.0 (credit "MedCE Hub" with a link), code MIT

## What is inside

| Data | Count | Endpoint |
|---|---|---|
| CME conferences and CE meetings | 540 | [`/v1/conferences.json`](https://medce-hub.github.io/cme-conferences-api/v1/conferences.json) |
| One conference | | `/v1/conferences/{id}.json` |
| CE / CME requirements (state × profession) | 634 records, 52 US jurisdictions, 13 professions | [`/v1/requirements.json`](https://medce-hub.github.io/cme-conferences-api/v1/requirements.json), `/v1/requirements/{profession}/{state}.json` |
| Professions | 13 | [`/v1/professions.json`](https://medce-hub.github.io/cme-conferences-api/v1/professions.json) |
| Specialties | 68 | [`/v1/specialties.json`](https://medce-hub.github.io/cme-conferences-api/v1/specialties.json) |
| States, mandatory topics, credit types | | `/v1/states.json`, `/v1/topics.json`, `/v1/credit-types.json` |

Conferences cover physicians (CME), nurse practitioners and physician assistants, nurses, pharmacists, dentists, psychologists, social workers, therapists and veterinarians. Every record has dates, city and state, format (in person, online, hybrid), CME cruises, CME / CE credits (AMA PRA Category 1, ANCC, AANP, ACPE, ADA CERP, RACE ...), price, organizer, official link and the date the facts were checked on the official page.

Requirement records give the hours per renewal cycle, mandatory topics such as opioid prescribing, implicit bias, human trafficking or domestic violence, how hours are reported (CE Broker, attestation), the state board and the legal source.

## Quick start

```bash
curl -s https://medce-hub.github.io/cme-conferences-api/v1/conferences.json \
  | jq '.data[] | select(.attributes.specialties | index("cardiology")) | .attributes | {title, start_date, city, state, credits_text}'

curl -s https://medce-hub.github.io/cme-conferences-api/v1/requirements/nurses/TX.json | jq '.data.attributes.rules'
```

A conference record (shortened):

```json
{
  "type": "conferences",
  "id": "veith-2026",
  "attributes": {
    "title": "VEITHsymposium 2026",
    "start_date": "2026-11-17",
    "end_date": "2026-11-21",
    "city": "New York",
    "state": "NY",
    "format": "in_person",
    "professions": [
      "physicians"
    ],
    "specialties": [
      "interventional-cardiology",
      "vascular-surgery",
      "cardiology"
    ],
    "credits_text": "46.25 AMA PRA Cat 1 · 46.25 ANCC CH",
    "official_url": "https://veithsymposium.org/general_info.php",
    "medcehub_url": "https://medcehub.com/events/veith-2026"
  },
  "links": {
    "self": "https://medce-hub.github.io/cme-conferences-api/v1/conferences/veith-2026.json"
  }
}
```

The files are static, so the API has no server side filters: download a collection and filter it in your code. GitHub Pages sends `application/json`; the body is a JSON:API document.

## MCP server for AI assistants

Tools:

| Tool | What it does |
|---|---|
| `search_conferences` | Find CME conferences by words, profession, specialty, state, format, CME cruise, mandatory topic and dates |
| `get_conference` | Full record of one conference |
| `get_ce_requirements` | CE / CME requirements for one profession in one state |
| `list_reference` | Valid ids for professions, specialties, states, topics, credit types |

Claude Desktop, Claude Code or any MCP client (Node 18+):

```json
{
  "mcpServers": {
    "medcehub": {
      "command": "npx",
      "args": ["-y", "github:MedCE-hub/cme-conferences-api"]
    }
  }
}
```

Claude Code: `claude mcp add medcehub -- npx -y github:MedCE-hub/cme-conferences-api`

Docker: `docker run -i --rm ghcr.io/medce-hub/cme-conferences-api` (the same server as an image; listed in the official MCP Registry as `io.github.MedCE-hub/cme-conferences-api`)

Example questions: "Which cardiology CME conferences are in Florida in spring 2027?", "Nurse practitioner conferences 2027 with pharmacology hours", "CME cruises next year", "How many CE hours does a Texas RN need and which topics are mandatory?"

## Sources and accuracy

Facts come only from the official page of the conference, its organizer or the state licensing board; each record has `official_url` or `source_url` and `checked_at`. Rules change: always confirm a renewal requirement with the state board before you rely on it. Found a mistake or want your conference listed? Write to info@medcehub.com or use [Add your conference](https://medcehub.com/add-your-conference). Listing and corrections are free.

## Attribution

Please credit **MedCE Hub (medcehub.com)** and link to the `medcehub_url` of the record you use.

## More on MedCE Hub

* [CME conferences 2026 and 2027](https://medcehub.com/cme-conferences)
* [Nurse practitioner conferences](https://medcehub.com/nurse-practitioner-conferences)
* [CME requirements by state](https://medcehub.com/cme-requirements)
* [Nursing CE requirements by state](https://medcehub.com/nursing-ce-requirements)

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: search_conferences returns matching conferences, get_conference returns a single full record, get_ce_requirements returns state licensing requirements, and list_reference provides valid filter IDs. There is no overlap between searching, detail retrieval, requirements lookup, and reference enumeration.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (search_, get_, list_). Singular/plural distinctions (get_conference vs search_conferences) are semantically appropriate and predictable.

Tool Count5/5

Four tools are well-scoped for a focused CME conference and CE requirements server. Each tool earns its place: search, detail retrieval, requirements lookup, and reference discovery are the minimal set for the domain.

Completeness4/5

The surface covers core read-only workflows: finding conferences with filters, getting conference details, retrieving license renewal requirements, and discovering valid filter values. Minor gaps exist (e.g., no explicit bulk listing of all conferences or multi-state requirement comparison), but agents can work around them by calling search or list_reference.