Studio Ninja MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key (get it at https://cotlet.dev/app). Required for tool calls; without it a tool call answers: "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.
Studio Ninja through Cotlet.dev. Call studio_ninja_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 |
|---|---|
| studio_ninja_guideA | How to work in Studio Ninja (leads, jobs, contracts, invoices and overdue payments): its screens and the sign-in link. Call this first. |
| studio_ninja_statusA | Check that your Cotlet.dev account and Studio Ninja are ready: account, credits and Studio Ninja connection. |
| studio_ninja_openA | Open a Studio Ninja page in your signed-in Cloud Browser (default https://studio-ninja.com) to work with leads, jobs, contracts, invoices and overdue payments. |
| studio_ninja_readA | Read the current Studio Ninja page: its text and numbered buttons, links and fields. |
| studio_ninja_clickB | Click a numbered element on the current Studio Ninja page. |
| studio_ninja_typeB | Type text into a numbered field on the current Studio Ninja page. |
| studio_ninja_closeA | Close the Studio Ninja 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 session lifecycle: readiness check (status), documentation (guide), navigation (open), inspection (read), and interaction (click/type/close). The closest pair, status vs. guide, is clearly separated by their descriptions (technical account/connection check vs. product how-to). No two tools could plausibly be selected for the same action.
All seven tools share the studio_ninja_ snake_case prefix with a single-word suffix, giving a highly predictable pattern. Minor deviation: status and guide are nouns while the rest are verbs (open/read/click/type/close), though the noun forms are conventional for informational tools.
Seven tools is well-scoped for a browser-driven SaaS automation surface: one per lifecycle stage (status, guide, open, read, click, type, close) with no redundancy. Nothing feels padded or thin.
Session lifecycle, navigation, page reading, and element interaction are all covered, forming a coherent read-then-act loop. Minor gaps remain: no explicit scroll or wait-for-load primitive for long/dynamic pages (e.g. overdue payment lists), no back/history navigation, and no dedicated select/keyboard action beyond click and type.