Gymvio 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 and exported as COTLET_API_KEY. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Gymvio through Cotlet.dev. Call gymvio_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 |
|---|---|
| gymvio_guideA | How to work in Gymvio (review client check-ins and workout logs, prepare training and nutrition plans and draft messages): its screens and the sign-in link. Call this first. |
| gymvio_statusA | Check that your Cotlet.dev account and Gymvio are ready: account, credits and Gymvio connection. |
| gymvio_openA | Open a Gymvio page in your signed-in Cloud Browser (default https://gymvio.com/login) to work with review client check-ins and workout logs, prepare training and nutrition plans and draft messages. |
| gymvio_readA | Read the current Gymvio page: its text and numbered buttons, links and fields. |
| gymvio_clickB | Click a numbered element on the current Gymvio page. |
| gymvio_typeC | Type text into a numbered field on the current Gymvio page. |
| gymvio_closeA | Close the Gymvio 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 workflow (guide, readiness check, open, read, click, type, close), so an agent can sequence them without guessing. The only mild overlap is between gymvio_guide and gymvio_status, both of which are pre-flight informational tools, but their descriptions clearly separate site instructions from account/credit/connection checks.
All seven tools share the gymvio_ prefix and a single lowercase suffix, giving a highly predictable namespace. The suffixes mix noun-style (guide, status) with verb-style (open, read, click, type, close) entries, a minor deviation that does not impede recognition.
Seven tools is well-scoped for a site-specific browser automation surface, with each tool earning its place as a primitive or onboarding step. Nothing is redundant and nothing feels arbitrarily withheld.
The core loop is covered: onboard, verify access, open a page, read its elements, interact via click and type, and close the session to stop credit usage. Gaps remain around scrolling long pages, explicit submit/keypress actions, and select-style widgets, which agents would have to work around with repeated read/click calls.