Skip to main content
Glama
README.md
# Breely MCP server

Connect Breely to ChatGPT, Claude and any AI agent through Cotlet.dev. Manage availability, blocked time, forms, invoices and client reports in your own signed-in Breely account. Write actions ask for approval by default.

## What you can ask

> Read revenue per service for last month.

> Draft an invoice for two massages and a hot stones add-on, then show me before sending.

> List blocked time for this week.

## Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.

### ChatGPT

Settings → Apps & Connectors → Create, with connector URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev. No API key needed.

### Claude

Settings → Connectors → Add custom connector, with URL `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 repo is a real MCP server. It speaks MCP over stdio, lists its Breely tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

Run the included Python module with Python 3.10 or later:

```bash
python3 breely_agent.py serve
```

Or with Docker:

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

Tools: `breely_guide`, `breely_status`, `breely_open`, `breely_read`, `breely_click`, `breely_type`, `breely_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+, with no third-party runtime dependencies. Clone this repository and run:

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

## Questions from Breely users

**Which Breely user should I connect?**

Sign in with the user whose work the agent should do. The agent sees what that user can see in Breely.

**Can the agent take card payments?**

Online payments use the Stripe or Square account connected in Breely. The agent can send an invoice or record a cash or bank transfer payment.

**Is Cotlet affiliated with Breely?**

No. Cotlet.dev is independent and not affiliated with Breely.

## Learn more

- [Breely integration and hosted tools](https://cotlet.dev/integrations/breely-api-mcp-server)

---

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

Request access: https://cotlet.dev/signup?app=breely&utm_source=github&utm_medium=readme&utm_campaign=breely

## Workflows on the hosted integration

The live integration page documents these 17 operations:

- `set_availability`
- `manage_blocked_time`
- `set_joint_appointments`
- `set_waitlisting`
- `cancel_appointment`
- `edit_form_questions`
- `manage_add_ons`
- `manage_automations`
- `manage_packages`
- `manage_subscriptions`
- `manage_coupons`
- `manage_gift_certificates`
- `manage_invoices`
- `record_payment`
- `run_report`
- `set_custom_fields`
- `ban_client`

The local stdio adapter exposes seven browser helpers listed above. These helpers forward to Cotlet.dev; the workflow operations are documented on the hosted integration page.

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct role: guide (instructions), status (readiness check), open/close (session lifecycle), and read/click/type (page interaction primitives). There is no meaningful overlap between any pair, and the 'call this first' hint on breely_guide further reduces ordering ambiguity.

Naming Consistency4/5

All seven tools share a uniform breely_ prefix and are short, lowercase, and single-token. The only minor deviation is that guide/status are nouns while open/click/read/type/close are verbs, but the pattern remains highly predictable.

Tool Count5/5

Seven tools is tightly scoped for a browser-automation wrapper: one onboarding pair, one session lifecycle pair, and three interaction primitives. Nothing feels redundant or missing at the count level.

Completeness4/5

The set covers the core browse loop (open, read, click, type, close) plus onboarding, which is enough to drive bookings, forms, and invoices. However, there is no explicit navigate/goto, scroll, or select-dropdown operation, so some flows depend on link-clicking or may dead-end on non-link controls.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues