Pike13 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Cotlet.dev API key used to authenticate with the hosted server. 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.
Pike13 through Cotlet.dev. Call pike13_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 |
|---|---|
| pike13_guideA | How to work in Pike13 (manage studio client records, class rosters, enrollment and reporting): its screens and the sign-in link. Call this first. |
| pike13_statusA | Check that your Cotlet.dev account and Pike13 are ready: account, credits and Pike13 connection. |
| pike13_openB | Open a Pike13 page in your signed-in Cloud Browser (default https://pike13.com) to work with manage studio client records, class rosters, enrollment and reporting. |
| pike13_readA | Read the current Pike13 page: its text and numbered buttons, links and fields. |
| pike13_clickC | Click a numbered element on the current Pike13 page. |
| pike13_typeC | Type text into a numbered field on the current Pike13 page. |
| pike13_closeA | Close the Pike13 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 in a browser-session workflow: guide (instructions), status (account/credit check), open (launch), read (snapshot page), click, type, close. The sequential read→click/type model leaves no realistic confusion about which tool to pick at any point.
All tools share a clear pike13_ prefix and are short, lowercase, and readable. Minor deviation: guide and status are nouns while open/read/click/type/close are verbs, so the pattern is not a pure verb_noun scheme.
Seven tools is tightly scoped to a single browser-automation workflow, with lifecycle tools (open/close), interaction tools (read/click/type), and onboarding aids (guide/status). Nothing feels padded or missing at the count level.
The surface covers the full session lifecycle and core page interactions (read, click, type) plus onboarding help and closing to stop credit usage. Gaps include no explicit navigate/scroll or select/dropdown handling, which agents may need on complex Pike13 screens.