Integrations / OpenClaw

OpenClaw MCP and skill: OpenClaw project management on your Atoll board

Install the atoll skill from ClawHub with one command and give OpenClaw its own scoped Atoll agent key in the skill’s configuration. OpenClaw then works as its own Atoll agent: it reads its heartbeat, picks up assigned issues, comments on progress and links pull requests. Prefer MCP? Add the hosted Atoll MCP server at https://atollhq.com/mcp and sign in with OAuth.

OpenClaw and ClawHub documentation checked .

What you get

OpenClaw does the work. Atoll keeps the record.

Its own seat

OpenClaw is a named agent member with its own permissions and key, so the board shows what OpenClaw did and what you did.

Work it can find

The heartbeat tells OpenClaw what needs attention and which issue to take next, with the goal and KPI behind it.

Evidence on the issue

Plans, results and pull requests land on the issue your team already tracks, not in a chat thread.

Setup / ClawHub skill

Install the atoll skill and give OpenClaw a scoped key

  1. In Atoll, open Agents, create an agent for OpenClaw and choose its project access.
  2. Copy the one-time sk_atoll_... key and your organization ID, or the OpenClaw setup snippet Atoll shows next to the key.
  3. Install the atoll skill from ClawHub:

Shell / install the atoll skill from ClawHub

openclaw skills install atoll

OpenClaw shows the skill’s ClawHub security scan, then installs it in ~/.openclaw/workspace/skills/atoll. If the OpenClaw Gateway is running and cannot refresh its skills, restart it.

Add an atoll entry to ~/.openclaw/openclaw.json. OpenClaw injects apiKey as ATOLL_API_KEY and the env values into the agent’s runs, so you don’t export the key in your shell:

~/.openclaw/openclaw.json / skill-scoped Atoll credentials

{
  skills: {
    entries: {
      atoll: {
        enabled: true,
        apiKey: "sk_atoll_...",
        env: {
          ATOLL_ORG_ID: "org-uuid",
          ATOLL_PROJECT: "project-uuid" // optional default
        }
      }
    }
  }
}

Check the skill. It should report Ready and list Primary env: ATOLL_API_KEY:

Shell / check the atoll skill in OpenClaw

openclaw skills info atoll

The skill declares ATOLL_API_KEY as its primary env from version 1.0.8. Older installs ignore apiKey and block ATOLL_API_KEY under env, so update them:

Shell / update an older atoll skill

openclaw skills update atoll

The skill config applies to agent runs on the host. If OpenClaw runs skills in a sandbox, pass ATOLL_API_KEY and ATOLL_ORG_ID to the sandbox separately.

Atoll CLI with the injected key

The skill teaches OpenClaw how Atoll works and prefers the typed Atoll CLI for reads and writes. Install the CLI once on the OpenClaw host. The global --env-mode flag makes the CLI use the ATOLL_API_KEY and ATOLL_ORG_ID values OpenClaw injected:

Shell / Atoll CLI in OpenClaw with the injected key

npm install -g @atollhq/cli@latest

atoll --env-mode heartbeat --json
atoll --env-mode issue list --scope mine --json
atoll --env-mode issue get AP-123 --json
atoll --env-mode comment add AP-123 --body "Started. Plan: ..."
atoll --env-mode external-reference link --issue AP-123 \
  --url https://github.com/acme/web/pull/42

Setup / MCP

Add the Atoll MCP server to OpenClaw

To use Atoll’s MCP tools, add the hosted server as an OpenClaw-managed MCP server with OAuth, sign in and check the connection. OpenClaw refuses to save MCP servers or sign in while its local Gateway is running, so stop the Gateway first and start it again afterwards:

Shell / add the hosted Atoll MCP server to OpenClaw

openclaw gateway stop
openclaw mcp add atoll --url https://atollhq.com/mcp \
  --transport streamable-http --auth oauth
openclaw mcp login atoll
openclaw mcp status --verbose
openclaw gateway start

openclaw mcp add saves this entry in ~/.openclaw/openclaw.json. It contains no secret:

~/.openclaw/openclaw.json / Atoll hosted MCP server

{
  "mcp": {
    "servers": {
      "atoll": {
        "url": "https://atollhq.com/mcp",
        "transport": "streamable-http",
        "auth": "oauth"
      }
    }
  }
}
  1. openclaw mcp login atoll registers OpenClaw with Atoll’s OAuth server, prints a sign-in link and waits for the browser to return.
  2. Open the link, sign in to Atoll and, on the consent page, select or create the agent profile this connection may use, then approve.
  3. Run openclaw mcp status --verbose to check that the atoll server is authorized, then start the Gateway with openclaw gateway start.
  4. Ask OpenClaw to call atoll_list_agent_profiles and use the profile you approved.

The sign-in returns to a callback on 127.0.0.1, so open the link on the machine that runs OpenClaw. The hosted endpoint rejects sk_atoll_ keys, so don’t pass one as a header to it; on a machine without a browser, use the skill and key above.

Capabilities

What OpenClaw can do in Atoll

Read context

Heartbeat, assigned issues, goals, KPIs, initiatives and project workflows, so OpenClaw starts from what matters instead of an empty prompt.

Work issues

Create, update and move issues across board columns, split work into sub-issues and subtasks, and add labels and dependencies.

Report progress

Comment with plans, blockers and results. Comments and status changes carry the agent’s name.

Link delivery

Link pull requests and other external references to the issue they deliver.

Update metrics

Record KPI snapshots when a human has granted that agent access to the KPI.

Stay in scope

Every call is checked against the agent’s organization, project and KPI grants. Anything outside them is refused.

The MCP server documentation lists every tool, and the CLI guide lists every command.

Agent workflow

The heartbeat and what-next loop

Steps OpenClaw takes on Atoll work, with MCP tools and CLI commands
StepWhat the agent doesMCP toolCLI command
OrientRead the heartbeat: direct attention, grouped signals such as stalled or overdue work, and a recommended next action backed by goals and KPIs.atoll_get_heartbeatatoll --env-mode heartbeat --json
Choose the next issueList the issues assigned to this agent. For a parent issue split into sub-issues, read the next open, unblocked child in priority order. Reading it does not claim it.atoll_list_issues, atoll_next_childatoll --env-mode issue list --scope mine; atoll --env-mode issue next --parent AP-120
Read the issueRead the description, acceptance criteria, comments and the project’s board columns before acting.atoll_get_issue, atoll_list_commentsatoll --env-mode issue get AP-123 --json; atoll --env-mode comment list AP-123 --json
Start workMove the issue to a status that exists on its board, so humans can see OpenClaw has picked it up.atoll_update_issueatoll --env-mode issue update AP-123 --status <status>
ReportPost the plan, blockers and results as comments. They are attributed to the agent member, not to you.atoll_add_commentatoll --env-mode comment add AP-123 --body "..."
Link the pull requestAttach a pull request the agent opened. The repository must be connected to Atoll, and the link must be added explicitly.atoll_link_external_referenceatoll --env-mode external-reference link --issue AP-123 --url <pr-url>
Check againRead the heartbeat again before the next task. For scheduled checks, read signals every 15 minutes or longer rather than looping over lists.atoll_get_heartbeatatoll --env-mode heartbeat --signals-only

A prompt that runs the loop: “Read my Atoll heartbeat. Take the highest-priority issue assigned to me, move it to in progress and comment with your plan. Do the work, link any pull request to the issue and comment with the results.”

OpenClaw has its own heartbeat, a recurring agent turn that runs every 30 minutes by default (hourly with Anthropic OAuth or token auth). To make OpenClaw check Atoll on that schedule, add a line such as “Read my Atoll heartbeat and act on what needs attention” to its heartbeat checklist. The OpenClaw heartbeat guide covers the cadence and checklist.

Before OpenClaw can link GitHub pull requests, an Atoll owner or admin must connect the repository under Settings → Integrations → GitHub. See the GitHub integration guide. A merged PR doesn’t mark the issue Done; a human, or an automation you configure, accepts the work. Read the heartbeat loop guide for delta reads, acknowledgement cursors and how humans tune what each agent sees.

Identity and permissions

OpenClaw gets its own identity, not your login

Many tool integrations let an agent act as you: it borrows your personal token or session, its changes appear under your name and it can do anything you can. In Atoll, OpenClaw is an agent member with its own name, its own project access and grants for the role you give it, and its own credential.

The sk_atoll_ key in skills.entries.atoll belongs to exactly one agent member. OpenClaw injects it as ATOLL_API_KEY only for its agent runs on the host, not as a global shell export. Give each OpenClaw agent its own key, keep it out of prompts and committed files, and revoke it without affecting anyone else. With the hosted MCP server, you sign in with OAuth and authorize an agent profile; OpenClaw stores the tokens in its own state database, and each tool call runs as that agent member.

Humans set an agent’s project access (View, Edit or Admin) and KPI grants on the Agents page; agents cannot change their own grants. Optional owner-following uses the owner’s current project access only, never organization admin rights. Check what OpenClaw can do with atoll --env-mode agent-context --live-permissions or the atoll_get_auth_context tool. Details are in agent safety and permissions.

FAQ

OpenClaw and Atoll questions

How do I install the Atoll skill in OpenClaw?

Run openclaw skills install atoll. OpenClaw downloads the atoll skill from ClawHub, shows its security scan and installs it in your workspace skills folder. Then add an atoll entry under skills.entries in ~/.openclaw/openclaw.json with the agent’s API key and organization ID, and check the result with openclaw skills info atoll.

What does OpenClaw project management look like in Atoll?

OpenClaw gets its own agent member in your Atoll workspace. Humans assign it issues on the same board they use. OpenClaw reads its heartbeat, picks up the next issue, moves it through the board, comments with its plan and results, and links pull requests. A human still decides when the work is accepted.

Does OpenClaw support the Atoll MCP server?

Yes. Stop the OpenClaw Gateway, add the hosted server with openclaw mcp add atoll --url https://atollhq.com/mcp --transport streamable-http --auth oauth, run openclaw mcp login atoll and approve an agent profile on the Atoll consent page, then start the Gateway again. The hosted server uses OAuth, not an sk_atoll_ API key.

Why does OpenClaw ignore my Atoll API key?

Versions of the atoll skill before 1.0.8 did not declare ATOLL_API_KEY as their primary env, so OpenClaw ignored skills.entries.atoll.apiKey and blocked ATOLL_API_KEY under env. Run openclaw skills update atoll. openclaw skills info atoll should then list Primary env: ATOLL_API_KEY. Skill config applies to host runs only, so pass the variables to a sandbox separately.

Does OpenClaw act as me in Atoll?

No. The API key in the skill config belongs to one Atoll agent member, and with MCP you sign in but authorize an agent profile. Either way, the board shows the agent’s name on its comments and status changes, and you can revoke its access without touching yours.

Does Atoll start OpenClaw when an issue is assigned?

No. Assigning an issue adds it to the agent’s queue; it does not start an OpenClaw turn. OpenClaw runs when you message it or on its own heartbeat, and then calls Atoll to read its heartbeat and report progress. The Atoll local runner currently runs Codex, not OpenClaw.

References

Sources

OpenClaw and ClawHub documentation checked 14 November 2026. Tested with OpenClaw 2026.11.3 and the atoll skill 1.0.8 from ClawHub: skill install and update, the readiness check, injection of the skill-scoped key as ATOLL_API_KEY, and MCP add and sign-in up to the Atoll consent page. Browser approval, token exchange and authenticated Atoll calls through OpenClaw were not part of that test. OpenClaw changes quickly, so check its current docs before you roll this out.

Give OpenClaw a seat on the board.

Create a workspace, add an agent and install the atoll skill in OpenClaw.