CoachingPortal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | No | Your Cotlet API key, obtained at https://cotlet.dev/app. Used for authentication when connecting via Claude Code, Cursor, the local stdio server, or Docker. Not required when adding https://cotlet.dev/mcp/v1 as a connector in ChatGPT or Claude and signing in with Cotlet.dev. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
CoachingPortal through Cotlet.dev. Call coachingportal_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 |
|---|---|
| coachingportal_guideA | How to work in CoachingPortal (review client check-ins and training programs): its screens and the sign-in link. Call this first. |
| coachingportal_statusA | Check that your Cotlet.dev account and CoachingPortal are ready: account, credits and CoachingPortal connection. |
| coachingportal_openB | Open a CoachingPortal page in your signed-in Cloud Browser (default https://app.coachingportal.io) to work with review client check-ins and training programs. |
| coachingportal_readA | Read the current CoachingPortal page: its text and numbered buttons, links and fields. |
| coachingportal_clickB | Click a numbered element on the current CoachingPortal page. |
| coachingportal_typeA | Type text into a numbered field on the current CoachingPortal page. |
| coachingportal_closeA | Close the CoachingPortal 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 has a clearly distinct role: guide and status are informational/setup, open/close manage the session lifecycle, and read/click/type are discrete page interactions. There is no meaningful overlap between tools.
All tools use the same coachingportal_ prefix followed by a concise verb or noun, forming a predictable and readable pattern. The convention is consistent throughout.
Seven tools are well-scoped for a browser-automation wrapper: setup guidance, status checking, session lifecycle, and the core read/click/type interactions. Each tool earns its place without unnecessary surface area.
The set covers the essential browser workflow—check readiness, open a page, inspect content, interact via click/type, and close the session. Minor gaps like explicit navigation, scrolling, waiting, or select handling exist, but agents can largely work around them with read and click.