Pirate Ship 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 from https://cotlet.dev/app. Used as a Bearer token to authenticate with the hosted Cotlet.dev MCP server (https://cotlet.dev/mcp/v1). Without it, tool calls fail with: "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.
Pirate Ship through Cotlet.dev. Call pirate_ship_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 |
|---|---|
| pirate_ship_guideA | How to work in Pirate Ship (shipments, rates and labels): its screens and the sign-in link. Call this first. |
| pirate_ship_statusA | Check that your Cotlet.dev account and Pirate Ship are ready: account, credits and Pirate Ship connection. |
| pirate_ship_openB | Open a Pirate Ship page in your signed-in Cloud Browser (default https://www.pirateship.com) to work with shipments, rates and labels. |
| pirate_ship_readB | Read the current Pirate Ship page: its text and numbered buttons, links and fields. |
| pirate_ship_clickB | Click a numbered element on the current Pirate Ship page. |
| pirate_ship_typeB | Type text into a numbered field on the current Pirate Ship page. |
| pirate_ship_closeA | Close the Pirate Ship 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 phase of browser work: onboarding (guide, status), session lifecycle (open, close), observation (read), and interaction (click, type). The boundaries between them are crisp, and the descriptions explicitly state when each should be used (e.g. guide says 'call this first').
All seven tools share the pirate_ship_ snake_case prefix, which makes them trivially groupable. The suffix mixes nouns (guide, status) with verbs (open, read, close, click, type), a minor deviation from a pure verb_noun pattern but still highly readable.
Seven tools is well-scoped for a single-site browser automation surface, with no filler. Each tool corresponds to an operation an agent actually needs: prepare, connect, observe, act, disconnect.
The surface covers the full session lifecycle plus read/click/type, which is enough to complete most shipment, rate, and label flows. Minor gaps remain (no explicit navigate-to-URL, scroll, or wait/press-enter tool), though open takes a URL and clicking handles most navigation.