Plancraft MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | API key obtained at https://cotlet.dev/app and exported as COTLET_API_KEY. Required for local stdio use and for header/API-key-based configurations; ChatGPT and Claude hosted connectors can alternatively sign in without an API key. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Plancraft through Cotlet.dev. Call plancraft_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 |
|---|---|
| plancraft_guideA | How to work in Plancraft (read projects, draft offers and invoices, review overdue payments and book working hours): its screens and the sign-in link. Call this first. |
| plancraft_statusA | Check that your Cotlet.dev account and Plancraft are ready: account, credits and Plancraft connection. |
| plancraft_openB | Open a Plancraft page in your signed-in Cloud Browser (default https://plancraft.com) to work with read projects, draft offers and invoices, review overdue payments and book working hours. |
| plancraft_readA | Read the current Plancraft page: its text and numbered buttons, links and fields. |
| plancraft_clickB | Click a numbered element on the current Plancraft page. |
| plancraft_typeB | Type text into a numbered field on the current Plancraft page. |
| plancraft_closeA | Close the Plancraft 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 browser action or lifecycle step: open, read, click, type, guide, status, close. The only mild overlap is among the startup tools (open vs. guide vs. status), but their descriptions clarify that guide provides instructions, status checks readiness, and open launches the page.
All tools share a consistent plancraft_ prefix, and most names are concise action verbs (open, read, click, type, close). The lone noun form plancraft_status and the guide noun-ish form are minor deviations from the otherwise verb-based convention.
Seven tools is well-scoped for a browser-automation server covering page lifecycle plus interaction primitives. Each tool has a clear operational role, with no redundant or filler tools.
The core browser loop is covered: open, read, click, type, and close, along with a guide and connection-status check. Minor gaps exist for common browser actions such as scrolling, keyboard shortcuts, or waiting for dynamic content, but agents can likely work around them.