PTminder 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. Required for local/stdio usage and for the Claude Code / Cursor header-based connection. Without it, tool calls answer: "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.
PTminder through Cotlet.dev. Call ptminder_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 |
|---|---|
| ptminder_guideA | How to work in PTminder (clients, sessions, workout plans, packages, payments and reports): its screens and the sign-in link. Call this first. |
| ptminder_statusB | Check that your Cotlet.dev account and PTminder are ready: account, credits and PTminder connection. |
| ptminder_openB | Open a PTminder page in your signed-in Cloud Browser (default https://ptminder.com) to work with clients, sessions, workout plans, packages, payments and reports. |
| ptminder_readA | Read the current PTminder page: its text and numbered buttons, links and fields. |
| ptminder_clickB | Click a numbered element on the current PTminder page. |
| ptminder_typeB | Type text into a numbered field on the current PTminder page. |
| ptminder_closeA | Close the PTminder 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 targets a clearly distinct step in the browser automation loop: guide (instructions), status (account check), open (launch), read (inspect), click (interact), type (input), close (teardown). There is no meaningful overlap, and the descriptions reinforce the sequence. An agent can easily select the right tool.
All seven tools share the ptminder_ prefix and use short snake_case action words. The convention is uniform and readable throughout, with only a trivial noun-vs-verb distinction between guide/status and open/read/click/type/close.
Seven tools is well-scoped for a browser automation server. The set covers the full interaction loop plus onboarding (guide) and account validation (status), with no redundant tools.
The open/read/click/type/close cycle provides a complete CRUD-style interaction loop for working on PTminder pages via a browser. Minor gaps remain, such as scrolling, screenshots, or explicit dropdown-select handling, but an agent can work around these through clicking and reading.