Skip to content

Documentation

Use Kicklace from Claude

Connect Claude, then set your workspace up by asking.

Connect Claude to your workspace and you can look people up, write notes, and set things up by asking. It's under Connections → Claude. The connection acts as you, does what you can do and no more, and is listed there under your own name. The MCP server is the protocol behind it.

What Claude can do

Look people up, read a person's whole story, run a report, add notes and follow-ups, put someone on a list with the words they agreed to, set up lists, stages and fields, and draft an email for you to send. The screen lists every tool, read straight from the ones Kicklace really has.

Four rules hold whatever you ask:

  • It never sends email. It writes a draft and gives you the link; a person presses send.
  • It never deletes. No record, note or consent record goes because Claude asked.
  • It never puts anyone on a list without the words they agreed to. The sentence is kept on the sign-up as the proof.
  • Everything is in your name. The timeline says "<you> via Claude", and every call is on the log.

Sending, deleting, removing a member, revoking a key and disconnecting something become a question for you instead, on Home with Approve and Decline. Only owners and admins decide, and a question nobody answers runs out after seven days.

Connecting it

Sign in from Claude

For claude.ai, Claude Desktop's connectors, and Claude on your phone. In Claude, go to Settings → Connectors → Add custom connector and paste:

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

Claude sends you to Kicklace to sign in. Choose All my workspaces (including ones you join later) or just one, and press Allow. That's all.

Or connect with a key

Claude Code, and some other apps, ask for a key instead. Connect with a key on the same screen makes one of your own. It's shown once; if you lose it, disconnect and make another.

Claude Code, in one line:

claude mcp add --transport http kicklace https://www.kicklace.com/api/mcp --header "Authorization: Bearer <key>"

Claude Desktop, in claude_desktop_config.json, then start Claude Desktop again:

{
  "mcpServers": {
    "kicklace": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.kicklace.com/api/mcp",
        "--header",
        "Authorization: Bearer <key>"
      ]
    }
  }
}

On macOS that file is ~/Library/Application Support/Claude/claude_desktop_config.json; on Windows it's %APPDATA%\Claude\claude_desktop_config.json.

Any other app that takes a key: the address above, and the header Authorization: Bearer <key>.

Seeing and ending a connection

Connected apps lists each sign-in and each key: the app, the workspace, when it was last used, and what it knows about. An app reads Kicklace's tool list once and keeps it, so a row says when an app is missing tools Kicklace added since; switching the connector off and on again in Claude fixes it. Disconnect ends a connection at its next call.

Things to ask

The screen starts with asks you can copy. None of them sends anything.

Ask What happens
"Who joined the waitlist this week, and what did they say?" Reads the people and their notes. Nothing changes.
"Add everyone who emailed me this week to Kicklace, with a note on what they wanted" Adds a person and writes one note for each, in your name. Needs Gmail connected in Claude.
"Put the people in this CSV on Product updates with the words they agreed to" Puts each one on the list with that sentence stored word for word. Without it, Claude is refused.
"Draft a welcome to the macOS waitlist for me to send" Writes the draft and gives you the link. Claude never sends.
"Read this LinkedIn profile and add them as a person" Adds one person with what the page says, and a note saying where it came from. Needs Claude's browser.
"Every Monday, brief me on the waitlist" Reads and sums up. Nothing changes. Needs Claude's scheduled tasks.
"Who downloaded but never activated?" Runs a report over your own stages and answers with the count.
"Which of my customers paid for the first time this month?" Runs a report over what your payments sent and answers with who. Nothing changes.
"Save a view of everyone still at Signed up" Adds the view to your Lifecycle's Table, live. Nothing is removed.
"Set up a Product updates list and write the welcome email for it" Makes the list with the sentence people will agree to, stored word for word, and saves the email as a template. Nothing is sent.

Where an ask leans on something outside Kicklace, like Gmail or Claude's browser, that's Claude's side of the connection, not Kicklace's.

What Claude did

The screen's log shows the last twenty calls: when, who, which tool, what it did, and whether it was refused. A row holds no address and no words of a note, only the tool's own summary, so the whole workspace can read it. Rows older than 30 days are deleted.

Above it, and yours only: what you asked Ask Kicklace inside the app, for thirty days.