bbotn Guide
botn app → KOENJA
Integrations · MCP connection

MCP connection (external LLM)

Query and manage your botn data straight from an LLM like Claude or Cursor. botn ships an MCP (Model Context Protocol) server.

What you can do

Once connected, the LLM can read this workspace's data and run sales tasks. Beyond reading, it creates contacts, deals and tasks — plus lead forms, auto follow-up sequences and campaigns — and can carry out real actions like sending an email campaign. e.g. “Summarize the hot leads to call today”, “Log a call note on this contact and create a follow-up task for tomorrow”, “Build a post-quote sequence and enroll this contact”.

Available tools

botn exposes 55 tools — full control, so the LLM can do nearly everything you do in the app. Read tools safely fetch data; action tools actually create, change and delete records.

Read (22)

Actions (33)

Action tools really change data. In particular, deletes (contacts, deals, tasks, notes) and sends (sequence enroll, email campaign) are hard to undo or push messages externally. Have the LLM act only on an explicit request, and confirm the target and content first. Every send honors marketing consent and unsubscribe policy automatically, and deletes are soft (recoverable).

1. Create a token

In Settings → MCP connection, press Create token. A botn_pat_… token is shown once — copy it (you can't see it again). The token is scoped to the workspace it was created in.

2. Connect your LLM

Most MCP clients connect to a remote server via the mcp-remote bridge. In Claude Desktop, add the following to your MCP config (JSON) and replace botn_pat_여기에_토큰 with your token. Node.js must be installed.

{
  "mcpServers": {
    "botn": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://botn.app/mcp",
        "--header", "Authorization: Bearer botn_pat_여기에_토큰"
      ]
    }
  }
}

Save, restart the client, and the botn tools appear. Cursor and other clients use the same URL (https://botn.app/mcp) and Authorization: Bearer header.

Security

A token acts only with its creator's workspace permissions, and only a hash is stored on the server. When you're done, revoke it in Settings → MCP connection — access stops immediately.

Treat the token like a password — don't paste it into code repos or chats. If in doubt, revoke and reissue. Every action applies only to the one workspace the token belongs to.