Blueprint MCP Server
# Blueprint MCP server for ChatGPT and Claude
Blueprint documents a Partner Platform API for partner organizations such as EHRs. No official Blueprint MCP server or ChatGPT or Claude connector was found, checked 19 November 2026.
Cotlet.dev connects ChatGPT, Claude and other AI agents to your own signed-in Blueprint clinician account.
Source: [Blueprint integration page](https://cotlet.dev/integrations/blueprint-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=blueprint).
## What can your agent do?
The live page describes 22 hosted tools: 2 reads and 20 writes.
Writes ask for confirmation by default, configurable per tool. Delete and merge actions always require approval.
Tools with an action parameter use list and get for reads; other actions write.
- `list_progress_notes`
- `list_note_templates`
- `write_session_summary`
- `update_session_details`
- `magic_edit_note`
- `revert_note_version`
- `sign_and_lock_note`
- `manage_snippets`
- `create_treatment_plan`
- `assign_assessments_worksheets`
- `delete_session_items`
- `set_session_transcripts`
- `create_appointment`
- `add_external_calendar`
- `transfer_client`
- `merge_client_profiles`
- `add_client_insurance`
- `manage_insurance_claims`
- `add_insurance_payment`
- `manage_superbills`
- `manage_services_fees`
- `set_sliding_scale_rate`
The agent sees the clients your Blueprint role can access. Live recording, dictation, telehealth, your Blueprint users and roles, and your subscription stay outside these tools.
Notes start from the session summary or transcript you provide. Review a note before approving its signature.
## Example requests
> List my client's progress notes.
> Draft a progress note from the session summary I provide.
> Show me the note before asking me to approve signing it.
> List insurance claims that need action.
## Connect ChatGPT and Claude
1. [Get access to Blueprint](https://cotlet.dev/signup?app=blueprint).
2. Enable Blueprint in the Cotlet.dev console and sign in at https://clinician.blueprint.ai/login in your Cloud Browser.
3. In ChatGPT, use Settings > Apps & Connectors > Create with `https://cotlet.dev/mcp/v1/connect` and OAuth.
4. In Claude, use Settings > Connectors > Add custom connector with the same URL.
## Connect Codex and Claude Code
Create an API key in the Cotlet.dev console and set `COTLET_API_KEY` in your environment.
Codex:
```toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```
Claude Code:
```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```
## Optional local MCP wrapper
Python 3.10+, standard library only. This repository provides seven generic browser helpers over Cotlet.dev: `blueprint_guide`, `blueprint_status`, `blueprint_open`, `blueprint_read`, `blueprint_click`, `blueprint_type`, `blueprint_close`.
These helpers are separate from the 22 hosted business tools above. Listing helpers needs no key; calling them requires `COTLET_API_KEY`.
```bash
export COTLET_API_KEY="your-key"
python3 blueprint_agent.py serve
```
For a local MCP client:
```json
{"mcpServers":{"blueprint":{"command":"python3","args":["/absolute/path/to/blueprint_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}
```
Other commands: `connect`, `status`, `guide`, `read`, `tools`.
The read command opens the browser, reads the page and closes the browser session.
## Access and independence
Use your own Blueprint account. You complete sign-in and any verification yourself.
Disable Blueprint for agents, reset the browser or change your Blueprint password to revoke access.
Cotlet.dev is independent and is not affiliated with, endorsed by or sponsored by Blueprint.
TDQS
Scored across 7 tools
Each tool maps to a distinct action in a browser session: open, read, click, type, close, plus guide and status for onboarding/readiness. The boundary between guide (how-to) and status (account/credit check) is clearly stated, and no two tools overlap in operation.
All tools share the blueprint_ prefix and snake_case, with mostly verb-based names (open, read, click, type, close). guide and status are noun-style names, a minor deviation from the otherwise consistent verb pattern.
Seven tools is well-scoped for a browser-automation server targeting a single clinical app. Each tool earns its place: session lifecycle, page interaction, plus two support tools for readiness and guidance.
The surface covers the core browser session lifecycle (open, read, click, type, close) and setup/status, leaving no obvious dead ends. Minor gaps exist, such as explicit navigation/scrolling or waiting tools, but agents can work around these with open and repeated read/click calls.