Pic-Time 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. Required for tool calls when running the server locally over stdio or connecting with the Authorization header. 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.
Pic-Time through Cotlet.dev. Call pic_time_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 |
|---|---|
| pic_time_guideA | How to work in Pic-Time (galleries, visitors, favorites, store orders and clients): its screens and the sign-in link. Call this first. |
| pic_time_statusA | Check that your Cotlet.dev account and Pic-Time are ready: account, credits and Pic-Time connection. |
| pic_time_openA | Open a Pic-Time page in your signed-in Cloud Browser (default https://pic-time.com) to work with galleries, visitors, favorites, store orders and clients. |
| pic_time_readA | Read the current Pic-Time page: its text and numbered buttons, links and fields. |
| pic_time_clickB | Click a numbered element on the current Pic-Time page. |
| pic_time_typeB | Type text into a numbered field on the current Pic-Time page. |
| pic_time_closeA | Close the Pic-Time 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 targets a distinct phase of the browser workflow: guide (reference), status (account check), open (session start), read (page inspection), click/type (interaction), and close (session teardown). There is no meaningful overlap; read vs. click vs. type are clearly separated by element type and action.
Every tool uses the identical `pic_time_` prefix followed by a single descriptive verb (guide, status, open, read, click, type, close). The pattern is fully predictable and no convention mixing occurs.
Seven tools is well within the ideal range and each maps to an essential step of a browser-driven workflow. Nothing appears redundant or padded, and the surface is small enough to be easily held in context.
The core loop of open → read → click/type → close is fully covered, including a guide and a readiness check. Minor gaps exist for common browser needs like scrolling, back navigation, waiting for page loads, or select/hover actions, but agents can largely work around these.