Connect an agent

A workspace token, not a public URL. Name the token after the bot. Point it at the live skill first.

Install

Create a token in settings. Name it after the bot (claude, cursor, grok). Then:

install
# Any MCP host
npx @becklabs/beck-mcp-server
# BECK_API_TOKEN=beck_…
# BECK_API_URL=https://beck.bot

Cursor, Claude Code, and Grok Bot all speak MCP. HTTP clients use the same token. More on MCP and API.

What the agent can do

Documents and Plan it. Recommend, start, log, finish, accept, reject — accept and reject follow the autonomy mode. Coordinator tokens can mint worker tokens. GitHub is a branch name and a PR URL on an epic, not an app install.

Do

One token per bot. Read https://beck.bot/skill.md before acting.

Don’t

Do not share a personal token across bots, and do not hand the agent a public document URL. There are none.

Questions

Does REST work too?

Yes. https://beck.bot/api/v1 with Authorization: Bearer beck_… and a workspace id. Same objects as MCP.

Are tokens Pro-only?

No. Tokens and your own keys work on Free.

$12 if you’re shipping. Free if you’re looking.

Pro is you and your agents, 250 credits. $15 a seat for the shared backlog. Cancel anytime.

See Plans

Free is 50 credits. Enough to see if the loop is real.