Use case
The workspace talks to the rest of your stack
The problem
What gets in the way
The board is the source of truth, then someone copies status into a script, a spreadsheet, and a chat. When an invoice is paid, the delivery tool does not hear it. Secrets live in a notes app because there was nowhere else to put them.
What changes
After you start using it
- 01
A scoped API key you create in the workspace and copy once
- 02
Webhooks that fire when tasks, invoices, or members change
- 03
MCP so Claude, ChatGPT, or an editor can work against that workspace
- 04
Workflows in the same workspace for jobs you already repeat
Workflow
Wire the workspace without a fifth tool
- 01
Open Developer. Create an API key with the scopes you need. Copy the secret once.
- 02
Add a webhook endpoint if another system should hear about invoices, tasks, or members.
- 03
Connect MCP for an agent, or build a workflow for a job you keep doing by hand.
What you use
Capabilities in this job
- 01
API keys, webhooks, MCP, and workflows
Create a scoped API key. Register a webhook. Connect MCP so Claude or ChatGPT can use the workspace. Build a workflow for a job you already repeat. There is no Slack or Jira integration, and no app marketplace.
- 02
Workspaces, projects, and boards
A workspace is the boundary for members and projects. A project holds statuses and tasks. The board is the live kanban view: columns are statuses, cards are tasks. Opening a task uses the inspector so you stay on the board.
Questions