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

# What can Klipy do over MCP?

> All 38 Klipy MCP tools, grouped by the OAuth scope that gates them: read, draft, write, and the gated send handshake for external agents.

The Klipy MCP server exposes 38 tools. Each is gated by one of the [nine scopes](/docs/guides/mcp/overview#scopes) — a tool only works if the caller consented to its scope during OAuth. Tools are grouped below by that scope.

<Note>
  Klipy MCP is supervised. Drafting is gated behind `comms:draft` and sending behind `messages:send`, and the two are separate steps: an agent can prepare an outbound message, but `send_message_draft` dispatches nothing without a fresh confirmation token from `prepare_message_send` and explicit human approval. Everything that could reach a prospect waits for you.
</Note>

Each row lists the tool, its action — **Read**, **Draft**, **Write**, or **Send** — and a one-line description.

## CRM read — `crm:read`

Read people, companies, deals, notes, tasks, segments, pipelines, views, and the CRM schema.

| Tool                  | Action | What it does                                                                                                                                      |
| --------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `search_crm_records`  | Read   | Search people, companies, deals, and notes by free-text query, across one record type or the common set.                                          |
| `list_crm_records`    | Read   | List records of one type newest-first, with per-type filters. Listing deals requires a pipeline id.                                               |
| `get_crm_record`      | Read   | Fetch a single CRM record by type and id.                                                                                                         |
| `describe_crm_schema` | Read   | Describe writable fields and verb support per record type, plus the organization's segments and pipelines, so ids can be resolved before writing. |
| `get_record_timeline` | Read   | Get the unified activity timeline (interactions and tasks) for a person, company, or deal.                                                        |
| `list_pipelines`      | Read   | List deal pipelines, each with its stages.                                                                                                        |
| `list_views`          | Read   | List saved views across contacts, companies, deals, and tasks.                                                                                    |

## CRM write — `crm:write`

Create, update, upsert, and delete CRM records, and link or unlink them.

| Tool                 | Action | What it does                                                                                                              |
| -------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------- |
| `create_crm_record`  | Write  | Create a new record from a data payload. A matching person or company is reported as a duplicate rather than overwritten. |
| `update_crm_record`  | Write  | Update an existing record by id with a partial patch; only the fields you pass change.                                    |
| `upsert_crm_record`  | Write  | Create-or-update a person (matched by email) or company (matched by domain) on its natural key.                           |
| `delete_crm_record`  | Write  | Permanently delete a record by type and id. Destructive and irreversible.                                                 |
| `link_crm_records`   | Write  | Attach a note to a person, company, or deal, or add a record to a segment.                                                |
| `unlink_crm_records` | Write  | Remove a link created by `link_crm_records`. Idempotent.                                                                  |

## Communications read — `comms:read`

Read message threads, interactions, and drafts.

| Tool                   | Action | What it does                                                                                          |
| ---------------------- | ------ | ----------------------------------------------------------------------------------------------------- |
| `search_interactions`  | Read   | Semantic search across email, meeting, and social interactions, returning citation-friendly snippets. |
| `get_interaction`      | Read   | Fetch a single interaction by its Klipy id or external thread/chat id.                                |
| `list_message_threads` | Read   | List the most recent email and social interaction threads, newest first.                              |
| `get_message_thread`   | Read   | Fetch a single thread, including its message payload.                                                 |
| `list_message_drafts`  | Read   | List your agent drafts, defaulting to those awaiting review.                                          |
| `get_message_draft`    | Read   | Fetch a single agent draft by id.                                                                     |

## Communications draft — `comms:draft`

Create, update, and discard message drafts. No tool here sends anything.

| Tool                    | Action | What it does                                                                                              |
| ----------------------- | ------ | --------------------------------------------------------------------------------------------------------- |
| `draft_email_message`   | Draft  | Create a suggested email draft for a human to review. Nothing is sent.                                    |
| `draft_social_message`  | Draft  | Create a suggested message draft on a connected social channel for a human to review. Nothing is sent.    |
| `update_message_draft`  | Draft  | Patch an existing draft's editable fields (body, dates, recipients, attachments). Nothing is sent.        |
| `discard_message_draft` | Draft  | Discard (reject) a draft so it can never be sent. The record is kept, marked rejected, for audit history. |

<h2 id="the-gated-send-handshake">
  The gated send handshake — `messages:send`
</h2>

Prepare and send an approved draft. This is the only path by which an MCP tool dispatches a real outbound message, and it takes two deliberate steps.

| Tool                   | Action | What it does                                                                                                                                                                            |
| ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `prepare_message_send` | Send   | Stage a draft and return the exact final outbound preview plus a single-use confirmation token (about a 5-minute lifetime). Sends nothing. Show the preview to the user before sending. |
| `send_message_draft`   | Send   | Send a previously prepared draft. Requires the confirmation token from `prepare_message_send` and is only called after the human has approved this exact message.                       |

## Meetings read — `meetings:read`

Read meetings, transcripts, recordings, and calendar events.

| Tool                        | Action | What it does                                                                  |
| --------------------------- | ------ | ----------------------------------------------------------------------------- |
| `list_meetings`             | Read   | List your meeting recordings, optionally within a time range.                 |
| `get_meeting`               | Read   | Fetch a single meeting, including its conferencing details and calendar link. |
| `get_meeting_transcript`    | Read   | Fetch a recording's transcript plus meeting and participant summary context.  |
| `search_meeting_recordings` | Read   | Keyword search over your meeting recordings.                                  |
| `list_calendar_events`      | Read   | List your scheduled bookings and meetings within a time range.                |

## Agent read — `agent:read`

Read the Klipy agent's pending suggestions and ask grounded questions.

| Tool                     | Action | What it does                                                                                                 |
| ------------------------ | ------ | ------------------------------------------------------------------------------------------------------------ |
| `list_agent_suggestions` | Read   | List the Klipy agent's pending suggestions — proposed CRM and task actions awaiting review.                  |
| `ask_klipy`              | Read   | Ask a grounded, read-only question over your CRM interactions, with citations back to the source. No writes. |

## Agent write — `agent:write`

Accept or reject the Klipy agent's suggestions.

| Tool                      | Action | What it does                                                                                               |
| ------------------------- | ------ | ---------------------------------------------------------------------------------------------------------- |
| `accept_agent_suggestion` | Write  | Accept a pending suggestion and apply its proposed CRM or task change, optionally overriding fields first. |
| `reject_agent_suggestion` | Write  | Reject a pending suggestion so it is never applied.                                                        |

## Account read — `account:read`

Read your identity, token usage, and booking links.

| Tool                 | Action | What it does                                                                                                                      |
| -------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------- |
| `get_current_user`   | Read   | Report your identity, organization, role, connected accounts, and consented scopes. Call this first to learn what a token can do. |
| `get_token_usage`    | Read   | Report your subscription tier, remaining token budget, and whether token consumption is suspended.                                |
| `list_booking_links` | Read   | List your scheduling and booking pages.                                                                                           |
| `get_booking_link`   | Read   | Fetch a single booking link by id.                                                                                                |

## Next steps

<CardGroup cols={2}>
  <Card title="Use cases" icon="lightbulb" href="/docs/guides/mcp/use-cases">
    Workflows that combine these tools end to end.
  </Card>

  <Card title="Troubleshooting" icon="life-buoy" href="/docs/guides/mcp/troubleshooting">
    Fix sign-in, missing tools, and scope errors.
  </Card>
</CardGroup>
