Swift Galleries 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. Used as a Bearer token for the hosted MCP server and as the env var for the local stdio server. Without it, tool calls return: "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.
Swift Galleries through Cotlet.dev. Call swift_galleries_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 |
|---|---|
| swift_galleries_guideA | How to work in Swift Galleries (clients, room photos, wall designs, sales reports and order downloads): its screens and the sign-in link. Call this first. |
| swift_galleries_statusA | Check that your Cotlet.dev account and Swift Galleries are ready: account, credits and Swift Galleries connection. |
| swift_galleries_openB | Open a Swift Galleries page in your signed-in Cloud Browser (default https://app.swiftgalleries.com) to work with clients, room photos, wall designs, sales reports and order downloads. |
| swift_galleries_readA | Read the current Swift Galleries page: its text and numbered buttons, links and fields. |
| swift_galleries_clickB | Click a numbered element on the current Swift Galleries page. |
| swift_galleries_typeB | Type text into a numbered field on the current Swift Galleries page. |
| swift_galleries_closeA | Close the Swift Galleries 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 of a browser workflow: guide (docs), status (account check), open/close (session lifecycle), and read/click/type (page interaction). The only mild overlap is between guide and status, both of which read as 'call first' orientation tools, but their described purposes are still separable.
Every tool uses the identical swift_galleries_ prefix followed by a single clear verb or noun (guide, status, open, close, read, click, type). The pattern is fully predictable and easy to infer new tools from.
Seven tools is well-scoped for a browser-driven SaaS integration: two orientation tools, two session lifecycle tools, and three page-interaction primitives. No tool looks redundant or filler.
The surface covers the core loop of open, inspect, interact, and close, which is sufficient for most tasks. Minor gaps exist around navigation to arbitrary URLs, scrolling long pages, and waiting for page load, but agents can largely work around these via open and repeated read.