soapnoteapi-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SOAPNOTEAPI_KEY | Yes | Bearer key for SOAPNoteAPI, e.g., snapi_sk_live_... or snapi_sk_test_... | |
| SOAPNOTEAPI_BASE_URL | No | Override API base URL | https://api.soapnoteapi.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_specialtiesA | List the medical specialties (and template variants) supported by SOAPNoteAPI. Use the returned specialty IDs as the |
| generate_soap_noteA | Generate a structured SOAP note (Subjective, Objective, Assessment, Plan) from a clinical transcript or shorthand. Optionally returns ICD-10/CPT/HCPCS billing-code suggestions and a plain-language patient summary. Billing codes are AI decision support and require clinician review. |
| get_noteA | Retrieve a previously generated note by its noteId. Useful for fetching the result of an asynchronous audio job once status is 'completed'. Notes auto-expire (see expires_at). |
| summarize_visitsA | Consolidate multiple past visits (SOAP notes and/or free-text summaries) into a longitudinal summary with key findings and active diagnoses. Useful for care coordination and chart prep. |
| transcribe_audio_to_soapA | Upload a local audio recording of a clinical encounter and get back a SOAP note. Short recordings return immediately; long ones process asynchronously — by default this tool waits and returns the finished note. Supported: mp3, m4a, wav, ogg, webm, flac. |
| get_audio_statusA | Check the processing status of an asynchronous audio-to-SOAP job by noteId. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: listing specialties, generating notes from text, transcribing audio, retrieving notes, checking status, and summarizing visits. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_specialties, generate_soap_note), making them predictable and easy to understand.
6 tools is well-scoped for a clinical note generation server. Each tool provides essential functionality without redundancy, covering the core workflow.
Covers the full lifecycle: specialty listing, note generation (text/audio), retrieval, status checking, and visit summarization. Minor gaps like lack of update/delete are acceptable given auto-expiration.