Iris Works 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, available 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.
Iris Works through Cotlet.dev. Call iris_works_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 |
|---|---|
| iris_works_guideA | How to work in Iris Works (review clients, schedule sessions and prepare invoices): its screens and the sign-in link. Call this first. |
| iris_works_statusA | Check that your Cotlet.dev account and Iris Works are ready: account, credits and Iris Works connection. |
| iris_works_openA | Open a Iris Works page in your signed-in Cloud Browser (default https://app.iris-works.com) to work with review clients, schedule sessions and prepare invoices. |
| iris_works_readA | Read the current Iris Works page: its text and numbered buttons, links and fields. |
| iris_works_clickB | Click a numbered element on the current Iris Works page. |
| iris_works_typeB | Type text into a numbered field on the current Iris Works page. |
| iris_works_closeA | Close the Iris Works 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 distinct role in a browser-automation workflow: guide, readiness check, open, read, click, type, and close. There is little risk of confusing one tool with another.
All tools use the same iris_works_ prefix and snake_case convention. The suffixes mix action verbs (open, read, click, type, close) with noun-like helpers (guide, status), but the pattern remains highly readable.
Seven tools is well-scoped for a browser-automation server. Each tool supports a necessary step in the session lifecycle, with no obvious filler.
The core loop is covered: check readiness, open a page, inspect it, click, type, and close. Some advanced browser operations such as scrolling, waiting, or navigation to arbitrary URLs may be missing, but basic workflows are supported.