ClinicSense MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key, obtained at https://cotlet.dev/app. Used to authenticate tool calls forwarded to the hosted Cotlet.dev server (exported as an environment variable, or sent as an `Authorization: Bearer` header). Tool calls without it return: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
ClinicSense through Cotlet.dev. Call clinicsense_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 |
|---|---|
| clinicsense_guideA | How to work in ClinicSense (appointments, wait lists, payments and financial reports): its screens and the sign-in link. Call this first. |
| clinicsense_statusA | Check that your Cotlet.dev account and ClinicSense are ready: account, credits and ClinicSense connection. |
| clinicsense_openA | Open a ClinicSense page in your signed-in Cloud Browser (default https://app.clinicsense.com) to work with appointments, wait lists, payments and financial reports. |
| clinicsense_readA | Read the current ClinicSense page: its text and numbered buttons, links and fields. |
| clinicsense_clickB | Click a numbered element on the current ClinicSense page. |
| clinicsense_typeB | Type text into a numbered field on the current ClinicSense page. |
| clinicsense_closeA | Close the ClinicSense 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 step in a browser session (guide, status, open, read, click, type, close) and the descriptions make the open-vs-read boundary clear. Minor potential for confusion between the informational tools (guide vs status), but the 'call this first' hint resolves ordering.
All tools share a consistent clinicsense_ prefix with short snake_case names, giving a predictable pattern. Slight deviation in that guide and status are nouns while open/read/click/type/close are verbs, but this is readable and unlikely to cause errors.
Seven tools is well-scoped for a single-app browser automation surface, with each tool covering a necessary phase of the session lifecycle. Nothing appears redundant or gratuitously granular.
The core loop (open page, read elements, click, type, close) plus onboarding guide and connection status covers the essential workflows for appointments, wait lists, and payments. Gaps exist for dropdown selection, key presses/submit, scrolling, or multi-tab handling, which agents may hit in richer booking flows but can often work around by clicking.