TeachMeHIPAA MCP Server
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@teachmehipaa/mcp
A local MCP server for the TeachMeHIPAA
Developer API. It lets an AI assistant (Claude Code, Claude Desktop, Cursor,
VS Code or any other MCP client) read and manage one organization's HIPAA
training through that organization's API client. It runs on your machine
over stdio and talks to the API through
@teachmehipaa/node.
Pre-release. The Developer API is not generally available, and neither@teachmehipaa/mcp nor @teachmehipaa/node is on npm yet, so the
npx -y @teachmehipaa/mcp commands below won't work until launch. Until
then, build from source and point your MCP client at
node /path/to/teachmehipaa-mcp/dist/cli.js instead. Names and behavior
can change before 1.0.
1. Create an API client
In the TeachMeHIPAA console, open Settings → Developer and create an API
client. Grant only the scopes the assistant needs (see Tools).
Copy the client id (cli_…) and the secret (tmh_cs_…). The secret is shown
once.
Start in the Sandbox. It is a separate deployment where learners never
get email, with its own API clients. Credentials work only in the
environment they were created in, so set TMH_ENVIRONMENT=sandbox for a
Sandbox client and leave it unset (or live) for a live one.
Related MCP server: trello-mcp
2. Register the server
Claude Code
claude mcp add teachmehipaa \
-e TMH_CLIENT_ID=cli_… \
-e TMH_CLIENT_SECRET=tmh_cs_… \
-e TMH_ENVIRONMENT=sandbox \
-- npx -y @teachmehipaa/mcpClaude Desktop
In claude_desktop_config.json:
{
"mcpServers": {
"teachmehipaa": {
"command": "npx",
"args": ["-y", "@teachmehipaa/mcp"],
"env": {
"TMH_CLIENT_ID": "cli_…",
"TMH_CLIENT_SECRET": "tmh_cs_…",
"TMH_ENVIRONMENT": "sandbox"
}
}
}
}Cursor
In .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every
project:
{
"mcpServers": {
"teachmehipaa": {
"command": "npx",
"args": ["-y", "@teachmehipaa/mcp"],
"env": {
"TMH_CLIENT_ID": "cli_…",
"TMH_CLIENT_SECRET": "tmh_cs_…",
"TMH_ENVIRONMENT": "sandbox"
}
}
}
}VS Code
In .vscode/mcp.json. VS Code uses servers and needs type. An inputs
entry makes VS Code ask for the secret and store it itself, so it stays out
of the file:
{
"inputs": [
{
"type": "promptString",
"id": "tmh-client-secret",
"description": "TeachMeHIPAA API client secret",
"password": true
}
],
"servers": {
"teachmehipaa": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@teachmehipaa/mcp"],
"env": {
"TMH_CLIENT_ID": "cli_…",
"TMH_CLIENT_SECRET": "${input:tmh-client-secret}",
"TMH_ENVIRONMENT": "sandbox"
}
}
}
}Keep the secret narrow
Most MCP client configs store the client secret in plain text, in a file
that other tools on your machine can read and that is easy to commit by
mistake. Create a separate API client for each assistant, grant it only the
scopes it needs, and revoke it in the console when you stop using it. Keep
project-level config files such as .cursor/mcp.json out of version
control, or use your client's secret prompt where it has one.
3. Check the connection
Ask the assistant to run whoami. It answers with the organization, the
API client, the granted scopes, the environment and when the access token
expires. If the token is a Sandbox (test) token while TMH_ENVIRONMENT is
live, or the reverse, whoami says so and tells you which value to set.
Configuration
Variable | Required | Default | Meaning |
| yes | API client id, | |
| yes | API client secret, | |
| no |
|
|
| no | An origin that replaces the environment's URL, such as a local mock: |
The organization comes from the access token, so it is not configured. A missing or invalid variable stops the server at start with a message on stderr that names the variable, never its value.
stdout carries the MCP protocol only. Diagnostics are JSON lines on stderr: the start-up line, one line per API response (method, path without its query, status, latency, request id) and one per failed tool call. They never contain the secret, an access token or a request or response body.
Tools
Tool | What it does | Scope |
| Organization, client, scopes, token expiry | none |
| Public course catalog | none (public) |
| Compliance totals and rate for one course |
|
| Learners by status, email or externalId, paged |
|
| One learner's status, dates, current certificate |
|
| Enroll one person (takes a seat, sends the invite) |
|
| Change name or externalId |
|
| Remove a person (destructive) |
|
| Email a reminder |
|
| Single-use, 5-minute sign-in URL for one learner |
|
| Certificate records, paged or for one learner |
|
| One certificate record |
|
| Public check of a tme.so verification link | none (public) |
| Seats held and free |
|
| The 30-day event log that webhooks deliver from |
|
| The audit trail |
|
Read tools are annotated readOnlyHint. update_learner and
offboard_learner are annotated destructiveHint, so clients ask before
running them. Writes that the API makes idempotent by key send a fresh
Idempotency-Key per call, reused on the SDK's own retries.
List tools return one page per call. Pass a page's nextCursor back as
cursor (as after for list_org_events) to read the next one.
There is no get_learner_by_external_id, because the API has no read by
external id. Use list_learners with externalId, which matches at most one
learner.
Errors
An API refusal comes back as a tool result with isError: true, never as a
protocol error, so the assistant can read it and act. The text is one line
with the status, the problem code, the title and detail, any field errors,
and a wait time for a 429:
403 [forbidden] Forbidden: missing scope learners:read.
422 [validation_failed] Validation failed. Fields: email: must be an email.
429 [rate_limited] Too many requests. Retry after 30s.structuredContent.error carries the same facts plus the requestId. Quote
that to support. Arguments that don't match a tool's schema come back as
Invalid arguments: … before any request is sent.
Deliberately excluded
These operations are not exposed, so an assistant cannot reach them through this server:
Webhook subscription management.
Certificate PDF download.
Seat purchasing.
Other Developer API operations, such as enrollments, members, CSV exports
and imports and bulk learner writes, have no tool. Use
@teachmehipaa/node
for those.
Build from source
Until both packages are on npm:
git clone https://github.com/TeachMeHIPAA/teachmehipaa-node.git
(cd teachmehipaa-node && npm ci && npm run build)
git clone https://github.com/TeachMeHIPAA/teachmehipaa-mcp.git
cd teachmehipaa-mcp
scripts/use-local-sdk.sh ../teachmehipaa-node
npm run buildThen use node as the command and the absolute path to dist/cli.js as its
argument, in place of npx -y @teachmehipaa/mcp. For Claude Code:
claude mcp add teachmehipaa \
-e TMH_CLIENT_ID=cli_… \
-e TMH_CLIENT_SECRET=tmh_cs_… \
-e TMH_ENVIRONMENT=sandbox \
-- node /path/to/teachmehipaa-mcp/dist/cli.jsRequires Node.js 20 or newer.
Support
Contact TeachMeHIPAA support with the requestId from the failed tool
result. Report vulnerabilities privately as described in
SECURITY.md. Changes are in the changelog;
CONTRIBUTING.md covers working on the server.
MIT licensed.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
HIPAA compliance AI agent — scan, grade, SRA, and generate compliance docs.
Query your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools.
Connect ChatGPT or Claude to your CRM, store or shipping API. Keys stay out of the chat.
Verified, pay-per-use API tools for AI agents through one authenticated connection.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read and modify an Acumulus administration through natural language over the official API, including invoices, picklists, and direct endpoint calls. Runs locally over stdio and supports test mode to validate writes without persisting them.427 PyPIAGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage Trello boards, cards, checklists, comments, and attachments over local stdio, with compact curated responses. Supports workspace allowlists, tool selection profiles, and an opt-in read-only mode for safer access.5GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to query authoritative medical APIs for drug information, health statistics, clinical guidelines, trials, and literature from sources such as FDA, WHO, PubMed, RxNorm, and Google Scholar, running locally without API keys.74 npmISC

Evo CRM MCPofficial
AlicenseBqualityBmaintenanceEnables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.17MIT