Eversports Studio Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet API key, obtained at https://cotlet.dev/app. It is used for local stdio usage and as the bearer token for hosted MCP connections. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Eversports Studio Manager through Cotlet.dev. Call eversports_studio_manager_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 |
|---|---|
| eversports_studio_manager_guideA | How to work in Eversports Studio Manager (review studio activities, manage attendance and email invoices): its screens and the sign-in link. Call this first. |
| eversports_studio_manager_statusB | Check that your Cotlet.dev account and Eversports Studio Manager are ready: account, credits and Eversports Studio Manager connection. |
| eversports_studio_manager_openB | Open a Eversports Studio Manager page in your signed-in Cloud Browser (default https://app.eversportsmanager.com) to work with review studio activities, manage attendance and email invoices. |
| eversports_studio_manager_readA | Read the current Eversports Studio Manager page: its text and numbered buttons, links and fields. |
| eversports_studio_manager_clickB | Click a numbered element on the current Eversports Studio Manager page. |
| eversports_studio_manager_typeA | Type text into a numbered field on the current Eversports Studio Manager page. |
| eversports_studio_manager_closeA | Close the Eversports Studio Manager 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-automation lifecycle: guide (documentation), status (account/connection check), open (navigate), read (page snapshot), click, type, and close. The only mild adjacency is guide vs. status, but their descriptions clearly separate 'how to work' from 'is my account ready'.
All seven tools use the same snake_case prefix `eversports_studio_manager_` followed by a short verb (guide, status, open, read, click, type, close). The pattern is entirely predictable and readable.
Seven tools is a tight, well-scoped set for a single-site browser automation surface; every tool earns its place and nothing looks redundant. No filler or speculative operations are present.
The core loop (open → read → click/type → close) plus onboarding and status checks covers the stated purpose. Minor gaps exist for common browser interactions such as scrolling, selecting from dropdowns, or waiting for page load, which agents may have to work around with repeated read/click calls.