Blueprint API and MCP server Let your AI agent finish the notes and the claims.

Blueprint's API is a Partner Platform for EHRs and other partner apps, and no Blueprint MCP server was found (checked 19 Nov 2026). Cotlet runs a hosted Blueprint MCP server with 22 tools that ChatGPT and Claude use in your own clinician account. Signing a note, submitting a claim and anything a client receives wait for your OK.

  • Free 7-day trial, no card
  • Unofficial, not affiliated with Blueprint

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Blueprint. Blueprint is a trademark of its owner. If Blueprint's own integrations cover what you need, use them first.

Blueprint Cloud Browser

22 tools Read and write

Practice paperwork

What can your AI agent do in Blueprint? The documentation and billing that follow each session.

  • Turn your session notes into a progress note

  • Sign and lock the notes you approved

  • Draft a treatment plan and assign a measure

  • Book recurring client appointments

  • Submit and resubmit insurance claims

  • Post payments, superbills and sliding-scale rates

Partner API, no MCP

Does Blueprint have an MCP server or an API? The official Blueprint routes, checked 19 November 2026.

Blueprint documents a Partner Platform API at developer.blueprint.ai. It lets a partner organization, typically an EHR, create clinicians and clients and get session documentation back, with a clientId, clientSecret and apiKey that Blueprint provisions. No Blueprint MCP server and no official ChatGPT or Claude connector was found.

  • Partner credentials come from your Blueprint representative, one set for sandbox and one for production.
  • The Partner API reference covers organizations, clinicians, clients, sessions, progress notes and assessments. It lists no endpoints for appointments, insurance claims, payments or superbills.
  • The Enterprise plan lists custom EHR integrations and API access; Alongside your EHR and All-in-one EHR are the self-serve plans.
  • Blueprint's own AI assistant works inside Blueprint, not from ChatGPT or Claude.
The Blueprint Partner Platform, working by hand and Cotlet compared
What you need Partner Platform APIBy handCotlet
Ask ChatGPT or Claude to do the work No MCP server found Copy and paste Hosted MCP server
Work in your own clinician account Built for partner apps Your login Your login, once
Calendar, claims, payments and superbills No endpoints listed One screen at a time 22 tools, writes after your OK
Run from n8n or a script Partner credentials, your own code Manual only REST, same key

Checked 19 Nov 2026. Sources: Blueprint developer docs: Getting started · Blueprint Partner API reference index · Blueprint pricing · Blueprint Help Center · Help: How to access your Progress Notes · Help: Review Other Clinician's Notes as a Supervisor · Help: Progress note templates · Help: Write Session Summary · Help: How to document a Couple's session · Help: How to document a Family session · Help: Update session details after a Progress Note · Help: Update session attendees, type and identified patient · Help: Magic Edit and Memory · Help: Revert to a previous version of a Progress Note · Help: How to sign and lock a Progress Note · Help: How to create and use Snippets · Help: How to create a Treatment Plan · Help: Delete notes, transcripts, sessions and treatment plans · Help: Enable or disable Transcripts · Help: Assigning Assessments and Worksheets · Help: Unassigning Assessments and Worksheets · Help: How to create a client appointment · Help: How to add an external calendar · Help: Transfer a client to a different clinician · Help: How to merge duplicate client profiles · Help: How to add client insurance information · Help: How to create and submit insurance claims · Help: How to resubmit insurance claims · Help: Secondary insurance and secondary claims · Help: How to add external insurance payments · Help: How to create and manage Superbills · Help: How to create services and set default fees · Help: How to set a sliding scale rate

Set up once

How does the Blueprint MCP server work? The Blueprint MCP server by Cotlet: your agent works in your own Blueprint account.

  1. 1Log in to Blueprint

    Once, in a browser we host for you.

  2. 2Connect your AI agent

    One address in its settings.

  3. 3Hand it the notes

    Paste your session summary, then read the note before it is signed.

Your agent works in your own signed-in Cloud Browser. Signing, claims and anything a client receives wait for your OK. Who can see your session

Any MCP client

How to connect Blueprint to your AI agent

  1. 1

    Sign in to Blueprint in a Cloud Browser. Open clinician.blueprint.ai in your Cotlet Cloud Browser and log in with your own clinician account.

  2. 2

    Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.

  3. 3

    Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.

Blueprint shares https://cotlet.dev/mcp/v1 with every other app you turn on, so the connector you add once also reaches your calendar or accounting apps. Turned Blueprint on later? Refresh the connector and the 22 Blueprint tools show up.

ChatGPT
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Claude
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
Cursor
// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}
Codex
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: blueprint_read
2 read, 20 write

All 22 Blueprint MCP tools

One tool per clinician workflow in the Blueprint Help Center. Tools with an `action` read with `list` and `get`; every other action writes and asks first.

Progress notes8

Read notes, write one from your summary or a pasted transcript, refine it, go back a version and sign it. Live recording, dictation and telehealth stay with you in Blueprint.

  • list_progress_notes List a client's sessions and read the progress note of one of them. read

    Opens the client's profile, the Sessions tab and View Progress Note, as Blueprint documents it. A clinician sees their own clients; the Admin role sees every client profile and the Supervisor role sees the clients of their supervisees. It changes nothing and runs without asking.

    MCP callblueprint_read → list_progress_notes

    REST endpointGET https://cotlet.dev/api/v1/blueprint/progress-notes

    Parameters

    Parameters: list_progress_notes
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string string ISO date of the session whose note you want. Leave empty to list the sessions only.
    clinician string string For admins and supervisors: the clinician whose clients you are reviewing.

    Example input

    {
      "client": "client"
    }

    Example response

    {
      "client": "Jordan Example",
      "sessions": [
        {
          "date": "2026-11-17",
          "note_type": "SOAP",
          "locked": false
        },
        {
          "date": "2026-11-10",
          "note_type": "SOAP",
          "locked": true
        }
      ],
      "note": {
        "date": "2026-11-17",
        "note_type": "SOAP",
        "sections": [
          "Subjective",
          "Objective",
          "Assessment",
          "Plan"
        ],
        "version": "v1"
      }
    }
  • list_note_templates List the progress note types your Blueprint clinic can use. read

    Returns the note types offered in your account, for example SOAP, DAP, BIRP, GIRP, EMDR, Case Management, Intake and SIRP, plus any custom template your clinic has. Use the name in write_session_summary or update_session_details. It changes nothing and runs without asking.

    MCP callblueprint_read → list_note_templates

    REST endpointGET https://cotlet.dev/api/v1/blueprint/note-templates

    Parameters

    No parameters.

    Example response

    {
      "note_types": [
        "SOAP",
        "DAP",
        "BIRP",
        "GIRP",
        "EMDR",
        "Case Management",
        "Intake",
        "SIRP"
      ]
    }
  • write_session_summary Start a session with the Write session summary method and generate its progress note. writeAsks first

    Blueprint turns the summary into a structured progress note; it needs at least 30 words. Use it when the client did not consent to recording, the session was a phone call, or you already have notes. The agent writes only what you give it. The note stays unsigned until sign_and_lock_note. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → write_session_summary

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/session-summary/write

    Parameters

    Parameters: write_session_summary
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    summary string required string Your notes, bullet points or a pasted transcript, at least 30 words.
    session_type string string `individual`, `couples` or `family`. Couples and family sessions file one note in the chart of the identified patient.
    attendees array array For couples and family sessions: each client or contact who attended.
    note_type string string A name from list_note_templates, for example SOAP or DAP.

    Example input

    {
      "client": "Jordan Example",
      "summary": "Client reported fewer panic episodes this week, two instead of five. Practiced paced breathing daily. Discussed work stress and avoidance of team meetings. Introduced a thought record for meeting worries. Client agreed to attend one meeting and log thoughts before next session.",
      "session_type": "individual",
      "note_type": "SOAP"
    }

    Example response

    {
      "client": "Jordan Example",
      "session_date": "2026-11-17",
      "session_type": "individual",
      "note_type": "SOAP",
      "note_generated": true,
      "locked": false
    }
  • update_session_details Change a session's note type, session type, approach, setting, times, attendees or identified patient. writeAsks first

    Changing the note type, session type or treatment approach regenerates the progress note; the earlier version stays in the version list. Start and end time update the session and its calendar event without touching the note. Changing the identified patient replaces a draft claim or invoice, so a submitted claim or issued invoice must be cancelled or voided first. Regenerating uses no extra Session Credit. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → update_session_details

    REST endpointPATCH https://cotlet.dev/api/v1/blueprint/session-details

    Parameters

    Parameters: update_session_details
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string required string ISO date of the session, for a client with more than one session read the time too (ISO date-time).
    fields object object Any of note_type, session_type, treatment_approach (for example CBT or EMDR), setting (telehealth or in-person), start_time, end_time, attendees, identified_patient.

    Example input

    {
      "client": "client",
      "session_date": "session date"
    }

    Example response

    {
      "client": "Jordan Example",
      "session_date": "2026-11-17",
      "note_type": "DAP",
      "regenerated": true,
      "version": "v2"
    }
  • magic_edit_note Give Blueprint an instruction to regenerate a note, and optionally save it to Memory. writeAsks first

    Magic Edit needs the session transcript; it is not available when transcripts are off or the transcript was deleted. A saved Memory applies to future notes of that note type, for example every SOAP note. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → magic_edit_note

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/edit-note/magic

    Parameters

    Parameters: magic_edit_note
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string required string ISO date of the session, for a client with more than one session read the time too (ISO date-time).
    instruction string required string What to change, for example "make the subjective section longer".
    save_to_memory boolean boolean Save the instruction to Memory so it applies to your future notes of the same type.

    Example input

    {
      "client": "client",
      "session_date": "session date",
      "instruction": "instruction"
    }

    Example response

    {
      "client": "Jordan Example",
      "session_date": "2026-11-17",
      "instruction": "Refer to the client as client, not patient",
      "saved_to_memory": true,
      "version": "v3"
    }
  • revert_note_version List a note's versions or switch it back to an earlier one. writeAsks first

    Blueprint keeps a version each time the note is regenerated by a new note type, session type, approach, Magic Edit or note preferences. Manual edits do not make a version. You can switch back to the newer version at any time. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → revert_note_version

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/note-version/revert

    Parameters

    Parameters: revert_note_version
    NameTypeDescription
    action string required string One of `list`, `revert`. `list` and `get` only read.
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string required string ISO date of the session, for a client with more than one session read the time too (ISO date-time).
    version string string For `revert`: the version to show, for example v1.

    Example input

    {
      "action": "action",
      "client": "client",
      "session_date": "session date"
    }

    Example response

    {
      "client": "Jordan Example",
      "session_date": "2026-11-17",
      "versions": [
        "v1",
        "v2",
        "v3"
      ],
      "current": "v1"
    }
  • sign_and_lock_note Sign and lock a finished progress note. writeAsks first

    A signed note is the clinical record and the condition for submitting an insurance claim. The agent signs only a note you have read and approved; a locked note shows an Unlock button in Blueprint if you need it later. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → sign_and_lock_note

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/and-lock-note/sign

    Parameters

    Parameters: sign_and_lock_note
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string required string ISO date of the session, for a client with more than one session read the time too (ISO date-time).

    Example input

    {
      "client": "client",
      "session_date": "session date"
    }

    Example response

    {
      "client": "Jordan Example",
      "session_date": "2026-11-17",
      "locked": true
    }
  • manage_snippets List, create, edit or delete the snippets you insert in notes with "/". writeAsks first

    Snippets live under My Account > Settings > Snippets. While editing a note you type "/" and the snippet name to insert the text. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → manage_snippets

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/snippets/manage

    Parameters

    Parameters: manage_snippets
    NameTypeDescription
    action string required string One of `list`, `create`, `update`, `delete`. `list` and `get` only read.
    name string string The shortcut, for example /nosi.
    content string string The full text the shortcut inserts.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "snippets": [
        {
          "name": "/nosi",
          "content": "No suicidal ideation, no homicidal ideation reported."
        },
        {
          "name": "/hw",
          "content": "Client agreed to complete the thought record before next session."
        }
      ]
    }

Treatment plans, measures and records4

Plans from the last three transcripts or an uploaded PDF, assessments and worksheets on a schedule, and the permanent deletes Blueprint offers.

  • create_treatment_plan Generate a treatment plan from a diagnosis and focus, or upload an existing PDF plan. writeAsks first

    Blueprint generates a plan from the client's last three session transcripts, so it needs those transcripts. Generation takes a couple of minutes; the agent returns the draft for your review before anything is signed. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → create_treatment_plan

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/treatment-plans

    Parameters

    Parameters: create_treatment_plan
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    method string required string `generate` or `upload`.
    diagnosis string string For `generate`: the diagnosis.
    focus string string For `generate`: the focus of treatment.
    file_url string string For `upload`: a link to the PDF. Uploaded plans are view only in Blueprint.
    sign_and_lock boolean boolean Sign and lock the plan after you have read it.

    Example input

    {
      "client": "client",
      "method": "method"
    }

    Example response

    {
      "client": "Jordan Example",
      "method": "generate",
      "diagnosis": "Generalized anxiety disorder",
      "status": "Review and Accept",
      "locked": false
    }
  • assign_assessments_worksheets List, assign or unassign a client's assessments and worksheets. writeAsks first

    The client starts receiving an assigned item at the frequency you set, and stops after unassign. Blueprint documents this on its Plus plan. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → assign_assessments_worksheets

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/assessments-worksheets/assign

    Parameters

    Parameters: assign_assessments_worksheets
    NameTypeDescription
    action string required string One of `list`, `assign`, `unassign`. `list` and `get` only read.
    client string required string Client name as it shows in your Blueprint Client List.
    kind string string `assessment` or `worksheet`.
    name string string Name or short name from the library, for example PHQ-9.
    frequency string string For `assign`: how often the client receives it, as Blueprint offers.

    Example input

    {
      "action": "action",
      "client": "client"
    }

    Example response

    {
      "client": "Jordan Example",
      "assigned": [
        {
          "kind": "assessment",
          "name": "GAD-7",
          "frequency": "Every 2 weeks"
        },
        {
          "kind": "worksheet",
          "name": "Thought record",
          "frequency": "Once"
        }
      ]
    }
  • delete_session_items Permanently delete a transcript, a note, a whole session or a treatment plan. writeAsks first

    Deleting in Blueprint is immediate and permanent; Blueprint keeps no copy. A session with a submitted claim or issued invoice cannot be deleted until the claim is cancelled or the invoice voided. Deleting transcripts stops Magic Edit and generated treatment plans for that client. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → delete_session_items

    REST endpointDELETE https://cotlet.dev/api/v1/blueprint/session-items

    Parameters

    Parameters: delete_session_items
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    item string required string `transcript`, `progress_note`, `session` or `treatment_plan`.
    session_date string string ISO date, for session items.

    Example input

    {
      "client": "client",
      "item": "item"
    }

    Example response

    {
      "client": "Jordan Example",
      "item": "transcript",
      "session_date": "2026-11-10",
      "deleted": true
    }
  • set_session_transcripts Turn the clinic's Session Transcripts setting on or off. writeAsks first

    Only the Admin role can change it, on a plan with documentation automation. With transcripts off, Magic Edit and generated treatment plans are not available; you can still upload a plan. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → set_session_transcripts

    REST endpointPUT https://cotlet.dev/api/v1/blueprint/session-transcripts

    Parameters

    Parameters: set_session_transcripts
    NameTypeDescription
    enabled boolean required boolean true keeps transcripts, false stops saving them.

    Example input

    {
      "enabled": true
    }

    Example response

    {
      "session_transcripts": false,
      "updated": true
    }

Calendar and clients4

Appointments with or without the client notification, an outside calendar beside them, transfers and merges of client profiles.

  • create_appointment Read your Blueprint calendar or create an appointment for a client. writeAsks first

    Blueprint creates the appointment only after Send notification or I'll send manually, so the agent asks you which one. With `list` it reads the week before booking so it does not double book. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → create_appointment

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/appointments

    Parameters

    Parameters: create_appointment
    NameTypeDescription
    action string required string One of `list`, `create`. `list` and `get` only read.
    client string string For `create`: the client.
    appointment_type string string Appointment type, as set up in Blueprint.
    start string string ISO date-time.
    end string string ISO date-time.
    location string string Telehealth or your office location.
    recurring string string Optional repeat rule, for example weekly.
    notify boolean boolean true sends the client the notification, false is I'll send manually.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "client": "Jordan Example",
      "appointment_type": "Individual therapy",
      "start": "2026-11-24T15:00",
      "end": "2026-11-24T15:50",
      "location": "Telehealth",
      "recurring": "weekly",
      "notified": true
    }
  • add_external_calendar Show an external calendar, such as Google Calendar, on your Blueprint calendar. writeAsks first

    The calendar appears under Other calendars and its events show on your Blueprint calendar, so the agent sees your personal events when it books. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → add_external_calendar

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/external-calendars

    Parameters

    Parameters: add_external_calendar
    NameTypeDescription
    calendar_type string required string The calendar type Blueprint offers, for example Google Calendar.
    share_link string required string The sharing link you copied from that calendar.

    Example input

    {
      "calendar_type": "calendar type",
      "share_link": "https://example.com"
    }

    Example response

    {
      "calendar_type": "Google Calendar",
      "listed_under": "Other calendars",
      "saved": true
    }
  • transfer_client Move a client to another clinician, or add or remove assigned clinicians. writeAsks first

    Uses the Actions menu on the client profile. A transfer changes who sees the client's chart. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → transfer_client

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/client/transfer

    Parameters

    Parameters: transfer_client
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    mode string required string `transfer` moves the client fully; `manage_assigned` adds or removes clinicians.
    clinician string required string The clinician to assign or remove.
    remove boolean boolean For `manage_assigned`: true removes the clinician.

    Example input

    {
      "client": "client",
      "mode": "mode",
      "clinician": "clinician"
    }

    Example response

    {
      "client": "Jordan Example",
      "mode": "transfer",
      "clinician": "Clinician B",
      "confirmed": true
    }
  • merge_client_profiles Merge a duplicate client profile into the one you keep. writeAsks first

    Both profiles must belong to the same clinic. Where they differ, the primary profile's values win. The merge is permanent: the secondary profile is deleted. The agent shows both side by side, with date of birth, email, phone and MRN, before it asks you. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → merge_client_profiles

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/client-profiles/merge

    Parameters

    Parameters: merge_client_profiles
    NameTypeDescription
    primary string required string The profile to keep.
    secondary string required string The duplicate to merge and delete.

    Example input

    {
      "primary": "primary",
      "secondary": "secondary"
    }

    Example response

    {
      "primary": "Jordan Example",
      "secondary": "Jordan Exmaple",
      "merged": true
    }

Insurance and billing6

Coverage on the client profile, claims from draft to resubmission, payments received outside Blueprint, superbills and your fees.

  • add_client_insurance Add a client's primary or secondary insurance to their profile. writeAsks first

    Sets billing mode to Insurance in the "How [client] pays" card first. Without insurance on file Blueprint creates no draft claims for the client's sessions. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → add_client_insurance

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/members/{member_id}/client-insurances

    Parameters

    Parameters: add_client_insurance
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    coverage string required string `primary` or `secondary`.
    payer string required string Insurance name as Blueprint lists it.
    member_id string required string Member ID, policy or subscriber number from the card.
    copay number number Co-pay, if you know it.
    claims_address string string For payers that route claims by address.
    policyholder string string Name of the policyholder if it is not the client.

    Example input

    {
      "client": "client",
      "coverage": "coverage",
      "payer": "payer",
      "member_id": "member_8c41d2"
    }

    Example response

    {
      "client": "Jordan Example",
      "coverage": "primary",
      "payer": "Example Health Plan",
      "member_id": "XEX123456789",
      "copay": 25,
      "saved": true
    }
  • manage_insurance_claims List claims that need action, then submit, resubmit, mark denied or close one, or submit a secondary claim. writeAsks first

    Blueprint creates a draft claim after each session for a client with insurance; claims stay drafts until submitted. Submitting needs electronic claims turned on and a signed note. A resubmission opens a new draft that replaces the original claim. A submitted claim goes to the payer and cannot be pulled back by the agent. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → manage_insurance_claims

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/insurance-claims/manage

    Parameters

    Parameters: manage_insurance_claims
    NameTypeDescription
    action string required string One of `list`, `get`, `submit`, `resubmit`, `mark_denied`, `close`, `submit_secondary`. `list` and `get` only read.
    client string string Client, for every action except `list`.
    session_date string string ISO date of service.
    reason string string For `mark_denied`: a short denial reason.
    primary_payment object object For `submit_secondary`: paid amount, adjustments and patient responsibility from the primary payer.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "needs_action": [
        {
          "client": "Jordan Example",
          "session_date": "2026-11-17",
          "status": "Draft",
          "billed": 150
        },
        {
          "client": "Riley Sample",
          "session_date": "2026-11-12",
          "status": "Denied",
          "billed": 150
        }
      ]
    }
  • add_insurance_payment Enter an insurance payment received outside Blueprint and post it to claims. writeAsks first

    Uses Billing > Insurance Payments. Per claim, insurer paid, patient responsibility, prior payment and write-off must add up to the total billed amount. The payment is posted only at Approve and Post, after your OK. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → add_insurance_payment

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/insurance-payments

    Parameters

    Parameters: add_insurance_payment
    NameTypeDescription
    payer string required string The insurance that paid.
    payment object required object Payment details as Blueprint asks for them.
    claims array required array Each claim with insurer_paid, patient_responsibility, prior_payment and write_off.

    Example input

    {
      "payer": "payer",
      "payment": "payment",
      "claims": "claims"
    }

    Example response

    {
      "payer": "Example Health Plan",
      "claims": [
        {
          "client": "Jordan Example",
          "session_date": "2026-11-03",
          "billed": 150,
          "insurer_paid": 110,
          "patient_responsibility": 25,
          "write_off": 15
        }
      ],
      "posted": true
    }
  • manage_superbills Create a superbill for a date of service, or turn monthly superbills on or off for a client. writeAsks first

    A superbill is the itemized receipt a client sends to their insurer. It appears in the client portal under Insurance reimbursement as soon as it exists. With monthly superbills on, Blueprint sends one to the client at the end of each calendar month. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → manage_superbills

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/superbills/manage

    Parameters

    Parameters: manage_superbills
    NameTypeDescription
    action string required string One of `create`, `monthly_on`, `monthly_off`. `list` and `get` only read.
    client string required string Client name as it shows in your Blueprint Client List.
    session_date string string For `create`: the date of service.

    Example input

    {
      "action": "action",
      "client": "client"
    }

    Example response

    {
      "client": "Riley Sample",
      "action": "monthly_on",
      "in_client_portal": true
    }
  • manage_services_fees List your services, or create or edit one with its CPT code, description and rate. writeAsks first

    Uses Settings > Services & Fees. A changed rate applies to future sessions; sessions already billed keep their values. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → manage_services_fees

    REST endpointPOST https://cotlet.dev/api/v1/blueprint/services-fees/manage

    Parameters

    Parameters: manage_services_fees
    NameTypeDescription
    action string required string One of `list`, `create`, `update`. `list` and `get` only read.
    cpt_code string string CPT code, or a name such as late cancellation fee if no code applies.
    description string string Short description, for example 30-minute psychotherapy.
    rate number number The full rate.

    Example input

    {
      "action": "action"
    }

    Example response

    {
      "services": [
        {
          "cpt_code": "90834",
          "description": "45-minute psychotherapy",
          "rate": 150
        },
        {
          "cpt_code": "90837",
          "description": "60-minute psychotherapy",
          "rate": 190
        },
        {
          "cpt_code": "Late cancellation fee",
          "description": "Late cancellation",
          "rate": 75
        }
      ]
    }
  • set_sliding_scale_rate Change a service's amount on one client's invoice so it becomes their rate. writeAsks first

    Blueprint remembers the edited amount for that client and service on future invoices. Your base rate and existing invoices stay as they are. By default you confirm each call; you can switch that off for this tool.

    MCP callblueprint_write → set_sliding_scale_rate

    REST endpointPUT https://cotlet.dev/api/v1/blueprint/sliding-scale-rate

    Parameters

    Parameters: set_sliding_scale_rate
    NameTypeDescription
    client string required string Client name as it shows in your Blueprint Client List.
    invoice string required string The invoice to edit, from the client's Billing tab.
    service string required string The service on the invoice.
    amount number required number The new amount.

    Example input

    {
      "client": "client",
      "invoice": "invoice",
      "service": "service",
      "amount": 1
    }

    Example response

    {
      "client": "Riley Sample",
      "service": "90834",
      "amount": 90,
      "applies_to": "future invoices for this client and service",
      "saved": true
    }
Encrypted, revocable

Who can see my Blueprint session, and how do I revoke it?

  • What we store

    Your signed-in Blueprint browser profile, AES-256-GCM encrypted, in Finland. Never your password.

  • What your agent gets

    The 22 Blueprint tools. The session cookie stays in the Cloud Browser.

  • What the session sees

    The clients your role opens: your own as a clinician, your supervisees' as a supervisor, every profile as an admin.

  • What no tool touches

    Your Blueprint users and roles, your subscription, live telehealth and session recording.

  • If Blueprint logs you out

    You log in again yourself, in the same Cloud Browser.

  • How to cut access

    Disable Blueprint for agents, reset the browser, or change your Blueprint password.

Cotlet never sees or stores your password: you type it yourself, and the agent only uses the session that login leaves behind. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).

20 tools ask first

Approvals, undo and mistakes Nothing is signed, submitted or sent to a client until you say so.

  1. 01 Take your summary Your words, at least 30 of them.
  2. 02 Generate the note write_session_summary picks the note type.
  3. 03 Show you the note list_progress_notes reads it back.
  4. 04 Sign after your OK sign_and_lock_note locks it, then the claim can go.
Fixing a Blueprint write that went wrong
ActionHow to put it right
Regenerated noteSwitch back with revert_note_version
Locked noteUnlock it in Blueprint, then edit
Appointment or feeCall the tool again with the earlier values
Submitted claimAlready with the payer: resubmit a corrected claim
Delete or mergePermanent in Blueprint, so it always waits for your OK

All 20 write tools ask first: by default you confirm each call, and you can switch that off per tool. The 2 read tools, notes and note templates, run at once.

MCP call
{
  "name": "write_session_summary",
  "arguments": {
    "client": "Jordan Example",
    "summary": "Client reported fewer panic episodes this week, two instead of five. Practiced paced breathing daily. Discussed work stress and avoidance of team meetings. Introduced a thought record for meeting worries. Client agreed to attend one meeting and log thoughts before next session.",
    "session_type": "individual",
    "note_type": "SOAP"
  }
}
REST
curl -X POST https://cotlet.dev/api/v1/blueprint/session-summary/write \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"client":"Jordan Example","summary":"Client reported fewer panic episodes this week, two instead of five. Practiced paced breathing daily. Discussed work stress and avoidance of team meetings. Introduced a thought record for meeting worries. Client agreed to attend one meeting and log thoughts before next session.","session_type":"individual","note_type":"SOAP"}'
Response
{
  "client": "Jordan Example",
  "session_date": "2026-11-17",
  "session_type": "individual",
  "note_type": "SOAP",
  "note_generated": true,
  "locked": false
}

The note comes back unsigned, so you read it before sign_and_lock_note runs. A script or n8n flow can make the same call over REST at /api/v1/blueprint with the same key and price, in JSON. Failed calls are free.

Pay per call

How much does the Blueprint MCP server cost?

About $28 a monthfor a therapist with 20 sessions a week, 4,820 credits. Your Blueprint plan stays as it is.

Illustrative month, our assumption: successful calls for this caseload
JobCallsCredits
Progress note from your session summary1 × 80800
Read the note back, then sign and lock it2 × 801,600
Weekly list of claims that need action1 × 440
Claim submissions1 × 60600
Appointments booked for new or moved clients1 × 12120
Insurance payments and resubmissions1 × 10100
Treatment plan and measures for a new client2 × 360
Cloud Browser, 30 days1,500
Total332 calls4,820

The smallest pack, 5,000 credits for $29, covers this month. A group practice with more clinicians uses more calls.

  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Your Blueprint plan and session credits apply as they are

Credit packs are one-time purchases, not a subscription. The month above is built from our own assumptions, not measured customer usage. Blueprint counts one session credit per session however often the note is regenerated.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Other options

Blueprint MCP server: other ways to connect What each route does for a therapy practice, and where it stops.

Other ways to work with Blueprint, checked 19 Nov 2026
OptionWhat it doesWhere it stops
Blueprint Partner PlatformAPI and embeddable UI that put Blueprint documentation inside a partner EHR.Credentials provisioned per partner organization; built for software vendors, not one practice.
Blueprint EnterpriseCustom plans with custom EHR integrations and API access.Annual contracts, arranged on a call with Blueprint.
Blueprint's AI assistantNotes, plans and support inside Blueprint.Works in Blueprint, not from ChatGPT, Claude or your scripts.
By handOpen each client and session in Blueprint.One screen at a time, after the last session of the day.

If you build an EHR or run an enterprise practice with Blueprint API access, use it: it is the vendor's own route. Cotlet fits a practice that wants ChatGPT, Claude or a script working in its own Blueprint account today, with nothing to host.

EU company, since 2019

Who runs Cotlet A company you can look up.

Take Group sp. z o.o. runs Cotlet, a software company registered in Poland, EU (VAT PL6342984273) and working since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Blueprint tools go to contact@cotlet.dev.

Blueprint MCP server: questions

How do I get access?

Sign up free at https://cotlet.dev/signup?app=blueprint, turn on Blueprint under Integrations in the console and log in at https://clinician.blueprint.ai/login in your Cloud Browser. Then connect your AI agent and hand it your first session summary. The trial needs no card.

Does Blueprint have an API?

Blueprint documents a Partner Platform API at developer.blueprint.ai for partner organizations, typically EHRs, with credentials Blueprint provisions; its Enterprise plan lists custom EHR integrations and API access (checked 19 Nov 2026). No Blueprint MCP server and no official ChatGPT or Claude connector was found. Cotlet does not use that API: it works in your own signed-in Blueprint account.

How is this different from Blueprint's own AI assistant?

Blueprint's assistant works inside Blueprint: it writes notes and drafts plans there. Cotlet lets ChatGPT, Claude or a script you choose work in your Blueprint account with the same tools over MCP or REST, next to your other apps.

Which Blueprint plan do the tools need?

The tools use what your plan shows you. Blueprint lists Alongside your EHR at $69 per seat and All-in-one EHR at $1.49 per session on its pricing page (19 Nov 2026); scheduling, insurance billing and invoices are listed in All-in-one. Assigning assessments and worksheets is documented for the Plus plan.

Can the agent record or run a telehealth session?

No. Recording, dictation and Blueprint telehealth need your microphone and camera, so they stay with you. The agent writes the note from a summary or transcript you give it, and handles the scheduling and billing around the session.

Which Blueprint login should I use?

Your own clinician login. The agent sees what your role sees: a clinician their own clients, a supervisor their supervisees' clients, an admin every profile. Clinic settings such as session transcripts need the Admin role.

Is the MCP server different from the REST API?

Only in how it is called. Both carry the same 22 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST.

Is Cotlet affiliated with Blueprint?

No. Cotlet is independent and not affiliated with Blueprint.

Hand your next Blueprint note to your agent.

Free 7-day trial with 2,000 credits, no card needed.