Is Klipy's API, webhook, and MCP access free?

Yes. All three ship on every plan, including Free, every CRM write made through the API costs 0 tokens, and MCP is generally available to any Klipy account with no separate plan or beta waitlist.

How do I get an API key?

Go to Settings → API in the Klipy app, choose the exact resource:action scopes you need (there is no ALL scope), pick organization-wide or user-bound access, and copy the klipy_live_* key; it's shown once, at creation.

What webhook events can I subscribe to?

Nine live lifecycle events today, including lead.captured, deal.created, deal.moved, and booking.created, managed through an embedded Svix console at Settings → Webhooks with signed payloads. deal.closed is documented but not currently wired; use deal.moved for the closed and won signal.

Can I connect an AI agent like Claude or ChatGPT?

Yes, point any OAuth-capable MCP client at https://api.klipy.ai/mcp. You'll see a consent screen with a checkbox per capability scope; the agent can only call tools tied to scopes you approve, and no outbound message sends without your explicit approval through the two-step confirmation handshake.

Do I need Zapier or Make to connect Klipy, or can I build it myself?

Either. Zapier and Make.com aren't bundled native connectors; both call the same REST API on a trigger and receive the same webhooks as a trigger source, so you can build a Zap or scenario with no code, or call the API and webhooks directly yourself.

Automation

Build on Klipy. API, webhooks and MCP, free on every plan

Connect your own code, webhooks, or AI agent to Klipy's REST API, Svix webhooks, and MCP server, no prebuilt connector required.

Start free See all integrations

Free on every plan

Connecting API, webhooks & MCP (Klipy build surface) is included on every Klipy plan, including Free. API access, webhooks, and the MCP server ship standard, with no add-on fee.

Quick answer

Klipy exposes three open build surfaces, free on every plan including Free: a REST API v2 for CRM records, Svix webhooks for nine live lifecycle events, and an OAuth MCP server with 38 tools across 9 scopes for AI agents. No prebuilt Zapier or Make app; build your own against the same API.

Ask ChatGPT Ask Perplexity Ask Claude

At a glance

What you need to know

38

MCP tools

9 OAuth capability scopes gate 38 tools, so an agent reads, and with approval, writes the same CRM records.

9

Webhook events

lead.captured, deal.created, deal.moved, booking.created, and more deliver signed payloads in real time.

$0

Free on every plan

REST API, webhooks, and MCP ship on every plan, including Free; only scale and controls are gated, not the surface itself.

What it does

Klipy exposes three open build surfaces: a REST API v2, Svix-managed webhooks, and an OAuth MCP server. There's no request-access gate on the surface itself, only on scale and controls.

The REST API v2 (base https://api.klipy.ai/api/v2) covers most of Klipy's CRM object model. Contacts, companies, deals, pipelines, tasks, notes, and segments are fully readable and writable. Interactions are readable and can be logged, create-only through the API, with no edit route. Meetings, recordings, and bookings are read-only, since they're sourced from calendar and call-recording integrations.

Webhooks, managed through an embedded Svix console, push lifecycle events to your endpoint in real time. Nine event types are live today, including lead.captured, deal.created, deal.moved, and booking.created (see webhook event types for the full list).

The MCP server exposes 38 tools gated across 9 OAuth capability scopes, so an external agent (Claude, ChatGPT, or any MCP client) can read, and with explicit approval, write the same records.

How it connects

Three self-serve paths, no sales conversation required.

API. Create a scoped key at Settings → API (app.klipy.ai/settings/api). Pick the exact resource:action scopes you need (there's no ALL scope), choose organization-wide or user-bound access, and copy the klipy_live_* secret shown once at creation. Authenticate every request with X-Klipy-Api-Key or Authorization: Bearer. Limits: 200 requests per minute per key, 1000 requests per minute per org, with optional Idempotency-Key support on POST and PATCH. Key rotation has a grace-window overlap; revocation returns a 401. See issuing API keys.

bash

curl https://api.klipy.ai/api/v2/contacts \
  -X POST \
  -H "X-Klipy-Api-Key: <key>" \
  -H "Idempotency-Key: 8f14e45f-ceea-4b0a-9127-1e2e3c3c1a1a" \
  -H "Content-Type: application/json" \
  -d '{"email": "person@example.com"}'

Webhooks. Open Settings → Webhooks in the app, use the embedded Svix console to create an endpoint, and enable organization-level delivery. Verify the svix-id, svix-timestamp, and svix-signature headers on every payload, and return a 2xx only after you've persisted the event.

json

{
  "type": "lead.captured",
  "object": "event",
  "data": {
    "id": "h7w8y2f1",
    "first_name": "Jordan",
    "last_name": "Patel",
    "email": "jordan.patel@acmeanalytics.com",
    "title": "Head of Growth",
    "company_name": "Acme Analytics",
    "company_domain": "acmeanalytics.com",
    "industry": "SaaS",
    "employee_count": 350,
    "estimated_revenue": 1200000,
    "city": "Austin",
    "state": "TX",
    "country": "US",
    "linkedin": "https://linkedin.com/jordan-patel"
  }
}

MCP. Point any OAuth-capable MCP client at https://api.klipy.ai/mcp. The first connection shows a consent screen with a checkbox per capability scope, and the agent can only call tools tied to scopes you approve. Outbound sends stay gated behind two explicit steps: prepare_message_send returns a single-use confirmation token, and send_message_draft only fires with that token and your approval. No agent dispatches a message on its own. See connecting other MCP clients.

No-code. Zapier and Make.com aren't bundled connectors either. Both call this same REST API on a trigger and receive these same webhooks as a trigger source, per Klipy's integrations FAQ. Wiring a Zap or a Make scenario is still a self-build against the mechanism above, just without writing the request yourself.

Use cases

What you can do with it

I can now push a webhook-captured lead into my own database or downstream tool the moment it lands.

The lead.captured webhook uses data.id as the dedupe key for real-time sync.

Lead.captured payload reference

I can now batch-import CRM records from an external system without hammering single-record calls.

The REST API's idempotent batch-create endpoint handles up to 100 items per call; check summary.failed since a 200 isn't atomic.

API v2 introduction

I can now connect an MCP-capable agent to read CRM context and draft follow-ups I review before anything sends.

Every change stays explicit and reviewable, gated behind prepare_message_send and send_message_draft.

MCP use cases

Trade-offs

Pros and cons

Pros

REST API, webhooks, and MCP are free on every plan, including Free; there's no request-access gate on the build surface itself, only on scale and controls.
Scoped API keys (resource:action, no ALL scope) plus an idempotent, non-atomic batch-create endpoint make bulk writes safe to retry.
Webhook deliveries are signed and managed through an embedded Svix console, with a dedicated doc page per event for payload shape.
The MCP send handshake is two explicit steps, prepare_message_send then send_message_draft with a single-use token, so no agent dispatches a message unsupervised.

Cons

No prebuilt Zapier or Make.com app. You, or a no-code builder, wire the trigger and action yourself against the raw API and webhooks.
deal.closed is a documented webhook event that isn't currently wired. Use deal.moved for the closed and won signal instead.
Batch-create isn't atomic: a 200 response can still contain per-item failures, so check summary.failed rather than trusting the status code alone.
Klipy's own public integrations FAQ still tells API applicants to contact support, language that's out of step with the self-serve Settings → API flow described above.

Sources