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 contacts, deals, tasks, organizations, campaigns, lists, offerings, notifications and pipeline report, and create/update contacts, notes, tasks and deals. e.g. “Summarize the hot leads to call today”, “Log a call note on this contact and create a follow-up task for tomorrow”.

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.