Do I have to paste a key?

Not from claude.ai, Claude Desktop or Claude on a phone: you add the address as a connector, Claude sends you back to Kicklace to sign in, and you pick the workspace. A client that asks for a key instead, like Claude Code, gets one from Settings → Claude in one button.

Can Claude email my customers?

No. It drafts an email and hands you the link, or it proposes a send that lands on the Approvals page with what would happen beside it and one button. There is no setting that changes this, and it is the same rule for the assistant inside the app.

What can it do without asking me?

Everything that can be undone: finding people, running reports, writing notes, tasks and records, moving somebody's stage, making lists, emails, stages, fields and views, and drafting an automation for you to switch on. Sending, destroying and cutting a key loose are the three it can only propose.

Can it see another workspace?

No. A connection is one member's, in one workspace, and can do exactly what that member can do there and no more. Disconnecting it on the same screen stops it at its next call rather than at the end of an hour.

How do I know what it did?

Every call it makes, refused or not, is one line under Settings → Claude: when, who it acted as, the tool, what it did in a sentence, and whether it worked. Every write carries your name and via Claude on the record's own timeline. No arguments are stored, so no address and no message body lands in that log.

What if I do not use Claude?

The same set of tools is the assistant inside Kicklace, so you can ask for the same things without a subscription anywhere. And nothing about the CRM needs either: the screens do everything the tools do, because the tools are built on them.

Kicklace, an AI-powered CRM for micro SaaS

MCP CRM

Kicklace speaks the Model Context Protocol. Point Claude at one address and it can look people up, run a report, set the workspace up and draft an automation — as you, and written down.

One address, and Claude is in your CRM

Claude Code, Claude Desktop, claude.ai, or any other client that speaks the protocol. There is nothing to install and nothing of ours running on your machine.

The connector address

https://www.kicklace.com/api/mcp

In Claude, that goes in Settings → Connectors → Add custom connector. Claude sends you back to Kicklace to sign in, you pick the workspace, and that is the whole of it — nothing is pasted and no key is copied. A client that would rather have a key, like Claude Code, gets one from Settings → Claude in one button.

What comes back is that member's, in that one workspace: it can do what they can do and no more. It is listed on the same screen as a connected app, with a Disconnect that stops it at once. A key made for a server rather than a person is read only, whatever it is asked for.

What it can do

Not a chat about your CRM. The same tools the app's own screens use, over your own workspace.

Look people up. Find them, read one person's whole story, search across everything, and see who is at which stage.
Run a report. Ask a question of your own data and get the answer; keep the good ones as charts on a dashboard, or as saved views in Contacts.
Write things down. Add a person or an organization, write a note, put a task on somebody's list, move a record, and put somebody on a list — with the words they agreed to, which it must be given.
Set the workspace up. Make the lists, the emails, the stages, the fields, the pipelines and the views your events then feed, connect your website's address, or install a whole starter in one call.
Write an automation. A sentence becomes a draft you read as When · Wait · Only if · Then, on your automations page like one the app wrote, and you turn it on.
Draft an email. It writes the words and hands you the link. You are the one who presses send.

What it never does

Four rules that do not have a setting. They are not configuration; they are the product.

It never sends an email. It drafts one, or it proposes one for you to approve. Nothing it does puts words in front of a customer without a person pressing something.
It never puts anybody on a list without the words they agreed to. A consent sentence has to be given, it is stored verbatim beside the subscription, and the source says it was added by you, via Claude.
It never deletes anything on its own, and it never mints or reads a key. Both are proposals, and a key it cannot read at all.
It never changes a setting beyond the one its item names. Allowing your website's address allows that address, and nothing near a sending domain or a plan is touched. It invites a member or changes a role directly, as an owner or admin would; removing one is a proposal.

The three acts that leave the building

Sending an email, destroying something, and cutting loose a key or a door your servers post to. A sent email cannot be recalled, a deleted record cannot be restored, and a revoked key breaks a running system.

So those three are neither refused nor done. Claude writes down what it wants in one sentence — “Claude wants to send Still on the waitlist to the people on Waitlist” — and it lands on an Approvals page with what happens if you approve beside it, and one button. Only an owner or an admin decides, a proposal expires after a week, and what is done in your name says so on the timeline: your name, proposed by Claude.

Everything else it just does. That is the whole division: the acts you cannot take back are paused, and the ones you can are not, because a CRM that asks permission for a note is a CRM nobody lets near anything.

And it is all written down

Not a log you have to go and find: the same screen you connected it on.

Every call it makes — refused or not — is one line under Settings → Claude: when, who it acted as, which tool, what it did in a sentence, and whether it worked. Every write it makes carries your name and “via Claude” on the record's own timeline, beside the things you did by hand. No arguments are stored, so no address and no message body ends up in that log.

The same set of tools is also the assistant inside the app, on ⌘J wherever you are, so a founder with no Claude subscription gets what a connector gives — and a tool added for one arrives in all of them the same day.

Questions

Do I have to paste a key?: Not from claude.ai, Claude Desktop or Claude on a phone: you add the address as a connector, Claude sends you back to Kicklace to sign in, and you pick the workspace. A client that asks for a key instead, like Claude Code, gets one from Settings → Claude in one button.
Can Claude email my customers?: No. It drafts an email and hands you the link, or it proposes a send that lands on the Approvals page with what would happen beside it and one button. There is no setting that changes this, and it is the same rule for the assistant inside the app.
What can it do without asking me?: Everything that can be undone: finding people, running reports, writing notes, tasks and records, moving somebody's stage, making lists, emails, stages, fields and views, and drafting an automation for you to switch on. Sending, destroying and cutting a key loose are the three it can only propose.
Can it see another workspace?: No. A connection is one member's, in one workspace, and can do exactly what that member can do there and no more. Disconnecting it on the same screen stops it at its next call rather than at the end of an hour.
How do I know what it did?: Every call it makes, refused or not, is one line under Settings → Claude: when, who it acted as, the tool, what it did in a sentence, and whether it worked. Every write carries your name and via Claude on the record's own timeline. No arguments are stored, so no address and no message body lands in that log.
What if I do not use Claude?: The same set of tools is the assistant inside Kicklace, so you can ask for the same things without a subscription anywhere. And nothing about the CRM needs either: the screens do everything the tools do, because the tools are built on them.

Join the waitlist

We are onboarding one company at a time. Leave your email and we will let you know when your workspace is ready.