Skip to main content
Glama
README.md
# Pike13 API and MCP server for ChatGPT and Claude

Pike13 documents Core, Reporting and Webhooks APIs. The Cotlet.dev page reports that no official Pike13 MCP server or ChatGPT or Claude connector was found in vendor sources checked on 12 November 2026. Cotlet.dev connects ChatGPT, Claude and other AI agents to your Pike13 business account through a hosted MCP server with 133 workflow tools. Tools marked Asks first wait for your approval.

## What you can ask

> Read tomorrow's class rosters.

> Find clients with unused passes.

> Review waitlisted clients for a session.

> Check the staff member assigned to an event.

> Read a client's visit history.

> Prepare the requested enrollment change for my review.

## Connect in 2 minutes

Start at https://cotlet.dev/signup?app=pike13, sign in to Pike13 with your own business account in your Cotlet Cloud Browser, and create an API key in the console for editors or scripts. Export the key as `COTLET_API_KEY`.

### ChatGPT

Settings → Apps & Connectors → Create, add connector URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev using OAuth.

### Claude

Settings → Connectors → Add custom connector, enter `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev.

### Claude Code

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

### Cursor

Copy `.cursor/mcp.json` from this repo into your project:

```json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

## Run it locally (stdio)

This repository provides a local MCP server with seven browser helper tools. It speaks MCP over stdio, lists those helpers without a key, and forwards calls to the hosted Cotlet.dev server. The hosted integration separately provides the 133 workflow tools listed on the live page. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

```json
{"mcpServers":{"pike13":{"command":"python3","args":["/absolute/path/to/pike13-mcp/pike13_agent.py","serve"],"env":{"COTLET_API_KEY":"your-key"}}}}
```

Or with Docker:

```bash
docker build -t pike13-mcp .
docker run -i --rm -e COTLET_API_KEY pike13-mcp
```

Tools: `pike13_guide`, `pike13_status`, `pike13_open`, `pike13_read`, `pike13_click`, `pike13_type`, `pike13_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

## Command line

Python 3.10+, nothing else to install. Clone this repository and run:

```bash
export COTLET_API_KEY="your-key"
python3 pike13_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 pike13_agent.py status    # is Pike13 ready in your Cotlet.dev account
python3 pike13_agent.py guide     # Pike13 screens and sign-in link
python3 pike13_agent.py read      # open Pike13, read the page, close the browser
python3 pike13_agent.py tools     # list Cotlet.dev tools
python3 pike13_agent.py serve     # start the stdio MCP server (same as no argument)
```

## Questions from Pike13 users

**Does Pike13 have an API or an official MCP server?**

Pike13 documents Core, Reporting and Webhooks APIs. The Cotlet.dev page reports no official Pike13 MCP server or ChatGPT or Claude connector in vendor sources checked on 12 November 2026.

**What can I do with the hosted Pike13 integration?**

The live page describes 133 workflow tools covering client records, scheduling, attendance, products, transactions and reporting. Your Pike13 staff permissions apply. The local server in this repository exposes seven browser helper tools and forwards calls to Cotlet.dev.

**Is this an official Pike13 integration?**

No. Cotlet.dev is independent and is not affiliated with, endorsed by or sponsored by Pike13.

## Source

[Pike13 integration and all 133 hosted workflow tools](https://cotlet.dev/integrations/pike13-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=pike13)

---

More: https://cotlet.dev/integrations/pike13-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=pike13

Start free: https://cotlet.dev/signup?app=pike13&utm_source=github&utm_medium=readme&utm_campaign=pike13

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.