Trainerize 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 to forward tool calls to the hosted Cotlet.dev server (without it, tool calls 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.
Trainerize through Cotlet.dev. Call trainerize_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 |
|---|---|
| trainerize_guideA | How to work in Trainerize (manage clients, programs, check-ins and messages): its screens and the sign-in link. Call this first. |
| trainerize_statusA | Check that your Cotlet.dev account and Trainerize are ready: account, credits and Trainerize connection. |
| trainerize_openB | Open a Trainerize page in your signed-in Cloud Browser (default https://trainerize.com) to work with manage clients, programs, check-ins and messages. |
| trainerize_readA | Read the current Trainerize page: its text and numbered buttons, links and fields. |
| trainerize_clickB | Click a numbered element on the current Trainerize page. |
| trainerize_typeA | Type text into a numbered field on the current Trainerize page. |
| trainerize_closeA | Close the Trainerize 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 browser-automation action (open, read, click, type, close) plus two informational tools. The only mild overlap is between trainerize_guide and trainerize_status, since both are 'call early' prerequisites, which could leave an agent briefly unsure which to invoke first.
All seven tools use a uniform trainerize_<verb> or trainerize_<noun> snake_case convention with short, unambiguous names. The pattern is fully predictable across the set.
Seven tools is well-scoped for a browser-driving server: a core action loop (open/read/click/type/close) plus onboarding and credential checks. No tool appears redundant or padding the surface.
The session lifecycle is fully covered from setup through read/act to teardown. Minor gaps remain for common browser needs such as explicit navigation to an arbitrary URL, scrolling long pages, and selecting dropdown options, which agents may have to work around via click/type.