monograph-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, obtained at https://cotlet.dev/app. Used to authenticate tool calls to the hosted Cotlet.dev server; 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.
Monograph through Cotlet.dev. Call monograph_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 |
|---|---|
| monograph_guideA | How to work in Monograph (architecture and engineering firm management with projects, staffing, budgets, time and billing): its screens and the sign-in link. Call this first. |
| monograph_statusA | Check that your Cotlet.dev account and Monograph are ready: account, credits and Monograph connection. |
| monograph_openB | Open a Monograph page in your signed-in Cloud Browser (default https://app.monograph.com) to work with architecture and engineering firm management with projects, staffing, budgets, time and billing. |
| monograph_readA | Read the current Monograph page: its text and numbered buttons, links and fields. |
| monograph_clickB | Click a numbered element on the current Monograph page. |
| monograph_typeC | Type text into a numbered field on the current Monograph page. |
| monograph_closeA | Close the Monograph 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: guide, readiness check, opening a session, reading the page, clicking, typing, and closing. The boundaries between setup, interaction, and teardown are obvious, with almost no risk of tool misselection.
All tools share the same monograph_ prefix and use short lower_snake_case names. The pattern is predictable throughout, with only guide/status being nouns and the rest actions, which is still highly consistent.
Seven tools are well-scoped for a browser automation wrapper: just enough to cover setup, page interaction, and cleanup. No tool feels redundant or out of place.
The set covers the core browser lifecycle: guide, status, open, read, click, type, and close. Minor gaps exist for general browser operations like scrolling, selecting dropdown options, or explicit navigation, but agents can likely work around them.