A CRM With a Built-In MCP Server and Action API

Your AI can talk about your CRM. It cannot use it.

A REST action API, a built-in MCP server and an in-app Copilot that all read the same capability registry — so your agents run the same actions your staff do, under scoped revocable keys, with the destructive ones classified so nothing sends, spends or deletes without a confirmation.

Start 30 days free $0 today · no contract · cancel any time

Unlimited calls, texts, emails and contacts

Everything else in Chirply comes with it

The problem is not that it is hard.

It is that nobody has the hours, and the cost of skipping it never shows up as a line on any invoice.

The integration always covers a tenth of the product

A public API that reaches contacts and deals and nothing else means your agent can do the easy part and stops exactly where the work begins — the call, the campaign, the booking, the invoice.

Two surfaces that disagree

When the API is a separate implementation from the app, they drift. A field the UI validates one way and the API another is a bug you find in production, on somebody else's data.

Autonomy with no brakes is not a feature

An agent that can send, spend and delete without a confirmation step is not a productivity tool. It is an incident waiting for a plausible-sounding prompt.

Set up once. It runs from then on.

Connect

Point your agent at the MCP server

The MCP server is built in — nothing to host, nothing to proxy. Bearer-authenticated with scoped, revocable API keys, so you grant exactly the reach you meant to and can take it back instantly.

Discover

Let it find its own tools

Catalog, search, describe and run, all under permanent action names. An agent lists what exists, reads what an action needs, and calls it — instead of you hand-writing a tool schema per endpoint and maintaining it forever.

Act

Reach the whole product, not a corner of it

Hundreds of documented reads and actions across every domain — because the API, the MCP server and the in-app Copilot all render from the same capability registry the app itself uses. There is no second implementation to drift.

Contain

Keep the dangerous ones behind a confirmation

Actions that send, spend or destroy are confirm-classified, so Copilot stops and asks before it does them. Your agent gets autonomy over the reversible work and a checkpoint on the rest.

Every piece of this is already live.

These are not roadmap items. Each one is running in production today, described here in the same words the full product catalog uses.

API & built-in MCP server

Your AI agents can drive Chirply directly.

The public REST action API, built-in MCP server, and in-app Copilot all read the same capability registry, so software can operate the same product people do.

Hundreds of documented reads and actions across every product domain
Catalog, search, describe, and run from the same permanent action names
Bearer-authenticated with scoped, revocable API keys
Confirm-classified actions stop Copilot before it sends, spends, or destroys

In-app Copilot

Ask for the outcome instead of hunting through menus.

A workspace-aware assistant can search Chirply, answer questions from live CRM context, and propose the same actions available throughout the app.

Searchable conversation history and workspace-specific context
Reads and actions come from the platform's documented capability catalog
Approval required before it sends, spends, publishes, or destroys
Past chats can be reopened or removed from one place

Webhooks & external API actions

Connect the odd system nobody has a native integration for.

Trigger a workflow from a signed public URL or call an outside API from inside a flow with configurable method, authentication, headers, query parameters, and body.

Incoming webhook trigger per workflow
Bearer, basic, and API-key authentication
JSON, form, raw, or automatic Chirply payloads
Merge fields work in URLs, headers, queries, and bodies

Outbound webhooks API

Your systems hear about events the moment they happen, instead of polling for them.

Register webhook endpoints against your API key and Chirply delivers platform events to them — signed, retried with backoff, and logged per delivery.

Subscribe any HTTPS endpoint to the events you care about, via /api/v1/webhooks or the capability surfaces
Every delivery is HMAC-signed; the signing secret is shown exactly once at creation and stored encrypted
Failed deliveries retry with backoff, with per-delivery status and error visible
Up to 200 active event-endpoint subscriptions per workspace

Bring your own Supabase

Own the database your funnels and apps write into.

Connect your own Supabase account and point workspaces, funnels or installed apps at your own projects. Chirply never bills you for the database, because Supabase bills you directly.

Connect by OAuth or a pasted access token, both encrypted server-side, with the token refreshing itself and falling back if OAuth is revoked
Create a real project in your own Supabase organization, in any of 17 regions, on your own card with nothing added on top
Link a backend per workspace, per funnel or per installed app, falling back to the workspace default
Only the anon key ever reaches the browser — the service-role key and database password stay encrypted on the server

Custom objects

Model the records your industry actually runs on, not just contacts and deals.

Define your own record types — properties, vehicles, policies, pets — with typed fields, then create, list, and link records under /objects like any built-in part of the CRM.

Text, number, date, boolean, select and more field kinds, with a chosen display label per type
The record form validates with the same rules the server enforces, in plain language
Records are workspace-scoped with row-level security like every other table
Full API, MCP and Copilot access through the same capability registry as the rest of the product

This is the part of Chirply that solves api & mcp server. See the other 14 areas — CRM, scheduling, messaging, automations, funnels, commerce, reputation and the rest — all included in the same workspace.

Try it on your own business for 30 days.

You do not have to migrate anything to find out whether this works. Start the trial, set up the one thing you came here for, and judge it on that.

$0 charged today. A card holds the workspace; nothing moves until day 30.

Unlimited usage. Calls, texts, emails and contacts are uncapped on every plan.

Your providers, your rates. Bring your own Twilio, Mailgun and AI keys and pay them directly — we do not mark usage up.

No contract. Cancel before day 30 and you are never billed.

Your trial runs on Scale, the top plan, so nothing is locked while you evaluate. If api & mcp server is all you need afterwards, Scale at $97/mo carries it — switch down before the trial ends and keep the lower price.

The questions everyone asks.

Which plan carries the MCP server?

Scale, at $97 a month — the plan your free trial already runs on — with unlimited API keys. The REST API and outbound webhooks start lower on Grow at $77, with two API keys.

Is the API a subset of what the app does?

No, and that is the point. The app, the REST API, the MCP server and Copilot all render from one capability registry, so an action exists everywhere or nowhere. Adding it in one place is what makes it appear in the others.

How do I stop an agent doing something expensive?

Keys are scoped and revocable, and actions that send, spend or destroy are confirm-classified — Copilot stops before performing them. You decide what a key can reach, and you can pull it in one click.

Can I get events pushed to me instead of polling?

Yes. Outbound webhooks deliver events to your endpoint as they happen, and workflows can call your own APIs with the method, authentication, headers and body you specify — so integration runs in both directions.

Can I keep the data in my own database?

On Scale you can bring your own Supabase and point workspaces, funnels and apps at your own Postgres. Every provider here is bring-your-own — your Twilio, your Mailgun, your model key, your database.

Weighing it against something specific?

Your AI can talk about your CRM. It cannot use it.