Kollabe
Retrospectives
Planning Poker
Standups
IceBreakers
Pricing
Dashboard
Public API · MCP server

Run your meetings
from your AI assistant.

Connect Claude, Cursor, or any MCP-compatible client to Kollabe and run a whole sprint from chat. Draft standups from yesterday's PRs, spin up planning poker from your backlog, and pre-seed retros with this week's incidents, all without leaving your editor.
View API docs
Claude · Kollabe MCP connected
M
Look at my GitHub PRs and Jira tickets from yesterday and draft my standup for today.
On it. Pulling yesterday's activity, then drafting your update.
github.list_prs{ author: "me", since: "2026-04-25" }
jira.search_issues{ assignee: "me", updated: "-1d" }
standup_list_questions{ standupId: "today" }
standup_submit_answers{ answers: [...] }
📝 Standup submitted · Mon Apr 27

Yesterday: Shipped KOL-412 (search rate-limit), reviewed 3 PRs.

Today: Pair on KOL-418 webhook retries with Sarah, draft RFC.

Blockers: Waiting on staging access for KOL-425.

Workflows

Three prompts your team will run every sprint.

Each one is a real workflow we've shipped with the MCP server. Tap a tab to see the prompt, the tools it hits, and what comes back.
For engineers · async standup prep

Draft today's standup from yesterday's PRs and tickets.

Every morning, hand the assistant your context. It reads your activity, formats answers, and submits them so you walk into the day with the standup already done.

Prompt

“Look at my GitHub PRs and Jira tickets from yesterday and draft my standup.”

Bridge: Your AI client's GitHub and Jira tools collect the activity. Kollabe formats and submits.
Tool sequence
1
github.list_prs{ author: "me", since: "yesterday" }
2
jira.search_issues{ assignee: "me", updated: "-1d" }
3
standup_list{ spaceId: "backend" }
4
standup_list_questions{ standupId: "today" }
5
standup_submit_answers{ answers: [...] }

Result. Standup submitted before standup. Three questions answered with linked PRs and ticket keys, ready for the team to read async.

Get connected

From zero to first tool call in five minutes.

OAuth-based, scoped to one organization, and revocable from settings at any time. No infrastructure to run or keys to rotate.
1

Add the MCP server

Drop the Kollabe MCP server URL into your AI client's settings (Claude Desktop, Cursor, Zed, ChatGPT, or your own script). Point it at kollabe.com/api/mcp.

2

Approve via OAuth

Sign in with your Kollabe account and approve the connection. The client issues tokens automatically and they last one year. No manual key wrangling or shared secrets.

3

Pick your organization

Choose which org the assistant should act in. Tokens are scoped to that single org and act on your behalf. Revoke anytime from Organization Settings → API Tokens.

Connect via MCP

Recommended

Works with any MCP-compatible client (Claude, Cursor, Zed, ChatGPT, or your own scripts). OAuth handshake on first connect.

URL
https://kollabe.com/api/mcp
Copy
Skills · Scripts · Public API

Build skills and scripts on top of the same API.

Need something more bespoke than a chat session? Issue a personal access token and call the public REST API directly from a Claude Skill, a CI job, a cron, or a one-off shell script. Same auth model, same endpoints.
Claude Skill

Drop a Kollabe Skill into your repo.

A Claude Skill is a tiny folder with a SKILL.md and a few helper scripts. Wire it to a Kollabe personal access token and Claude can run your team's exact rituals: your standup format, your retro columns, your action-item workflow.

.claude/skills/kollabe-standup/
SKILL.mdinstructions
submit.shcurl wrapper
.env.exampleKOL_TOKEN=...
API referenceMCP workflows →
Public API

One curl away from your sprint data.

Personal access tokens act as you. Bearer auth, JSON in/out, predictable shapes. Pick a permission level and an expiry, paste the token into your script, ship.

# .claude/skills/kollabe-standup/submit.shcurl -sS https://kollabe.com/api/v1/standups/today/answers \  -H "Authorization: Bearer $KOL_TOKEN" \  -H "Content-Type: application/json" \  -d "@./payload.json"

Scoped tokens

Every token belongs to one organization and acts as one user. No cross-org leakage or service accounts to babysit.

OAuth handshake

MCP clients connect via OAuth. No copy-pasting keys or .env files for end users. Tokens last one year and rotate cleanly.

Permission levels

Choose read-only, write, or admin per token. The assistant gets exactly the scope you give it. Nothing more.

Revoke anytime

Disconnect a client with one click from Organization Settings → API Tokens. Revoke the token and every active session dies instantly.