Blueprint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | API key created in the Cotlet.dev console. Required for Codex/Claude Code and for calling the local wrapper helpers; OAuth connectors use the hosted URL instead. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Blueprint through Cotlet.dev. Call blueprint_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blueprint_guideA | How to work in Blueprint (work with progress notes, treatment plans, appointments and insurance billing): its screens and the sign-in link. Call this first. |
| blueprint_statusA | Check that your Cotlet.dev account and Blueprint are ready: account, credits and Blueprint connection. |
| blueprint_openB | Open a Blueprint page in your signed-in Cloud Browser (default https://clinician.blueprint.ai/login) to work with work with progress notes, treatment plans, appointments and insurance billing. |
| blueprint_readB | Read the current Blueprint page: its text and numbered buttons, links and fields. |
| blueprint_clickC | Click a numbered element on the current Blueprint page. |
| blueprint_typeC | Type text into a numbered field on the current Blueprint page. |
| blueprint_closeA | Close the Blueprint browser session when the work is done, so credits stop running. |
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 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.