Sprout Studio MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Cotlet.dev API key used to authenticate with the hosted MCP server. Without it, tool calls return a message asking you to set 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.
Sprout Studio through Cotlet.dev. Call sprout_studio_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 |
|---|---|
| sprout_studio_guideA | How to work in Sprout Studio (photography inquiries, shoots, client paperwork, invoices and galleries): its screens and the sign-in link. Call this first. |
| sprout_studio_statusA | Check that your Cotlet.dev account and Sprout Studio are ready: account, credits and Sprout Studio connection. |
| sprout_studio_openA | Open a Sprout Studio page in your signed-in Cloud Browser (default https://sproutstudio.com) to work with photography inquiries, shoots, client paperwork, invoices and galleries. |
| sprout_studio_readB | Read the current Sprout Studio page: its text and numbered buttons, links and fields. |
| sprout_studio_clickB | Click a numbered element on the current Sprout Studio page. |
| sprout_studio_typeB | Type text into a numbered field on the current Sprout Studio page. |
| sprout_studio_closeA | Close the Sprout Studio 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 in the browser workflow: setup/help, readiness check, session open, page read, click, type, and close. The guide vs status distinction is slightly close but still clear from descriptions.
All tools use the same sprout_studio_ prefix and concise verb or noun naming pattern. The set is predictable and easy to scan.
Seven tools is a well-scoped set for a browser-based app automation workflow. Every tool earns its place, with no obvious redundant extras.
The surface covers the core browser lifecycle: guide, status, open, read, interact, and close. Minor gaps exist around navigation or richer interactions like scrolling, but the essential workflow is supported.