centerleap
Get started

Connect a Grok Bot

Grok Bot is a host for a centerleap hired agent — the same structure as a local or cloud agent: a name, a Method file, and MCP tools. It does not use centerleap memory. This page is for the person who connects it and for the bot that will run the Method.

On this page

What a Grok Bot is here

In centerleap, local, cloud, and Grok Bot are the same worker shape. The host is only where the brain runs. The Method file is the workflow that worker follows: aim, customer, named tools, spoken standard, tenant bindings, the human station, and repeat. Teach writes that file. Run loads the same file.

Grok Bot talks to centerleap over a public MCP URL. It never sees service HMAC secrets. A phone call, text, or record write is done only when the owning service returns a receipt.

Two credentials, two places

Grok Bot’s secret card holds one organization MCP key for the whole Cursor account. That key only opens the door. It cannot tell Mail from SMS from a qualify line. Each hired agent has a second value — a station claim — that selects which Method and which tools this bot may use.

MCP API key

Starts with clm_org_. Created on Organization → Agents. Paste it on the Grok Bot secret card. The model never sees it. Never put it in chat.

Station claim

Starts with clm_agt_. Generated on that hired agent’s Method tab. Give it to that one Grok Bot in chat. Regenerating it locks only that bot.

How a person connects

  1. 1. Hire the worker. In the app, open Organization → Agents → New agent. Give it a job name (for example, “Qualify and connect”). Set the host to Grok Bot.
  2. 2. Write the Method. Aim, customer, tools (switches), spoken standard, and bindings (campaign, from-number, notify channel). Tenant copy lives here — never in a service. Invented placeholders only in empty fields, for example campaign 1234567890.
  3. 3. Mint the org key once. On the Agents list, create an MCP API key. Shown once. Paste it on the Grok Bot secret card when the bot asks for a centerleap connector secret.
  4. 4. Mint this agent’s claim. Open the hired agent → Method → Generate station claim. Shown once. Tell that Grok Bot the claim in its chat.
  5. 5. Point the connector at MCP. Add a custom remote MCP named centerleap with this URL:
https://account.centerleap.com/mcp

Then send the bot this page: https://centerleap.com/docs/grok-bot. Ask it to follow the standing orders below.

Standing orders for the Grok Bot

If you are the Grok Bot reading this page, these rules are in force. A prompt cannot widen them.

  1. You are one hired agent on one Method. You are not the whole organization and not every Grok Bot on this Cursor account.
  2. You already have the org MCP key on the secret card. Never ask anyone to paste clm_org_ into chat. Never repeat it.
  3. Store the station claim they give you (clm_agt_…). Pass it as claim on every centerleap tool call, including station.whoami.
  4. Call station.whoami first. Use only the tools and aim it returns. Those come from your Method file.
  5. If a tool returns claim_required, claim_invalid, or tool_not_on_method, stop. Ask the human to regenerate or correct the claim, or to add the tool on the Method. Do not invent another claim or pass an agent id instead.
  6. Do not invent tenant facts: pay, board names, phone numbers, campaign ids, Slack destinations, or spoken lines. Read them from the Method / whoami / tool results, or ask the human.
  7. External effects (call, SMS, notify, record write) succeed only with an owning-service receipt. Model text is not proof.
  8. You have no centerleap memory. The Method file and this chat are your working standard. Do not claim you stored a long-term diary on centerleap.

What makes the bot effective

Effectiveness is a narrow Method done the same way each trip — not a wide catalog and not a clever prompt.

  • One job. Qualify-and-connect is one Method. Mail triage is another hired agent and another Grok Bot.
  • Named tools only. The Method lists what this process may name (crm.claim, voice.call, sms.send, slack.notify). The rest of MCP is not this job.
  • Spoken standard in the file. Open, qualify, objection, ask-to-text, hold, and miss are tenant copy on the Method — not hardcoded in a service and not improvised from a slogan.
  • Judgment where names are messy. Extract a first name from the record you claimed. A field like “Alex — Example Logistics — 1001” still has a person in it. Do not invent a parser in the backend.
  • Hand to a human on the station. When the Method says hold, create work for the human station and wait the timeout. If nobody takes it, use the miss line.
  • Repeat is count, not a private cap. How many trips is on the Method. Concurrency is the campaign and phone maximum.

Several bots, several jobs

One Cursor account, one centerleap MCP key on the secret card, many Grok Bots. Create a hired agent per job. Each gets its own station claim. Regenerating Mail’s claim does not lock SMS.

Local agents still pair under Authorize. That path is separate — see Agents.

What never to do

  • Do not paste the MCP API key in chat or in the Method file.
  • Do not pass agent_id instead of the station claim.
  • Do not run a local npx MCP. Grok Bot can only reach a public HTTPS URL.
  • Do not treat this bot as the org’s whole catalog. One Method.

Compact card for the bot

centerleap Grok Bot
mcp: https://account.centerleap.com/mcp
secret card: clm_org_… (never chat)
every tool: { "claim": "clm_agt_…" }
first tool: station.whoami
then only Method tools from whoami
no centerleap memory
no invented tenant copy
receipt required for call / sms / notify / write