> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coffeechats.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Tool reference

> Every Coffee Chats MCP tool, the permission it needs and the risk it carries.

The connector answers at `https://mcp.coffeechats.me/mcp` and publishes these 85 tools. This page is generated from the connector's tool catalogue, so it cannot describe a tool the connector does not have.

Every tool has two names. The machine name, such as `profile.get`, is the name an agent sends, and each tool below is headed with it. The title, such as "Get profile", is the name your agent host shows you, and each tool's own entry prints it.

## Tool families

| Family | Tools | Permissions | Page |
| - | - | - | - |
| Profile tools | 6 | `profile:read`, `profile:write` | [Profile tools](/mcp/tools/profile.md) |
| Booking tools | 9 | `booking:read` | [Booking tools](/mcp/tools/booking.md) |
| Contact tools | 16 | `contacts:read`, `contacts:write`, `research:run` | [Contact tools](/mcp/tools/contacts.md) |
| Meeting tools | 9 | `mail:read`, `meetings:read`, `meetings:transcript:read`, `meetings:write` | [Meeting tools](/mcp/tools/meetings.md) |
| Calendar tools | 4 | `integrations:read` | [Calendar tools](/mcp/tools/calendars.md) |
| Campaign tools | 6 | `campaigns:read`, `campaigns:write`, `mail:read` | [Campaign tools](/mcp/tools/campaigns.md) |
| Job tools | 12 | `jobs:read`, `jobs:write` | [Job tools](/mcp/tools/jobs.md) |
| Document tools | 5 | `documents:generate`, `documents:read`, `documents:write` | [Document tools](/mcp/tools/documents.md) |
| Billing tools | 5 | `billing:read` | [Billing tools](/mcp/tools/billing.md) |
| Booking page text tool | 1 | `profile:write` | [Booking page text tool](/mcp/tools/booking-page-text.md) |
| Booking page visibility tool | 1 | `profile:write` | [Booking page visibility tool](/mcp/tools/booking-page-visibility.md) |
| Booking scheduling rules tool | 1 | `profile:write` | [Booking scheduling rules tool](/mcp/tools/booking-scheduling-rules.md) |
| Booking event type tool | 1 | `booking:write` | [Booking event type tool](/mcp/tools/booking-event-type.md) |
| Booking event type archive tool | 1 | `booking:write` | [Booking event type archive tool](/mcp/tools/booking-archive-event-type.md) |
| Thank-you send tool | 1 | `mail:send` | [Thank-you send tool](/mcp/tools/meeting-thank-you-send.md) |
| Mail tools | 5 | `mail:read`, `mail:send`, `profile:write` | [Mail tools](/mcp/tools/mail.md) |
| Campaign pause tool | 1 | `campaigns:write` | [Campaign pause tool](/mcp/tools/campaign-pause-sending.md) |
| Action withdrawal tool | 1 | `profile:write` | [Action withdrawal tool](/mcp/tools/actions.md) |

## How risky a tool is

* `read`: This tool only reads your own data. It never changes anything and it never asks for your approval.
* `safe_write`: This tool changes one of your own settings as soon as the agent calls it. It does not ask you to approve first, because the change affects only your own account and you can set it back yourself.
* `consequential`: This tool cannot change anything on its own. It proposes the change, and nothing happens until you open the Coffee Chats page it points to and approve exactly what is shown.

## Rules every tool follows

* A tool reads only the account that authorized the connection. It cannot reach another student's data.
* A tool returns a bounded amount of text. Where a stored value can be too large to fit, the tool returns a measured fragment and a cursor, and the agent asks for the next fragment until there is none left. A tool's own page says whether it can do this at all.
* A read tool that fails returns a short message with no code. It says only that the call failed, except in two cases. A lookup that finds no record of yours names the kind of record it did not find, and a meeting whose transcript Coffee Chats does not hold says that instead. The [error codes](/mcp/errors.md) page gives all three texts.
* A tool that changes something either changes one of your own settings straight away, or proposes the change and waits for you to approve it in a browser.

## Endpoints that are deliberately not tools

These parts of Coffee Chats are reachable in the application and are deliberately not published as tools. Each name below is checked against the tool catalogue by name, and the connector registers no tool that answers to it.

* `billing.overage_settings.get`
* `booking.conflicts.dismiss`
* `booking.stats.get`
* `calendars.events.list`
* `campaigns.activity.list`
* `campaigns.credits.estimate`
* `campaigns.stats.get`
* `campaigns.template.preview`
* `contacts.match_or_create`
* `contacts.photos.bulk`
* `jobs.feed.list`
* `jobs.url.resolve`

Asking an agent for one of these by name does nothing. The connector has no such tool.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.