Let the board do the boring bits.

Rules that react to fifty kinds of events, from a moved card to an error that comes back. And for what rules can’t do: a REST API, webhooks and an MCP server for your AI assistant.

If this, then that.

1. Choose a trigger: A card that moves, a pull request that gets merged, an error spike, a deadline coming up, or simply Monday at 9.
2. Add conditions: Only in this list, only with this label.
3. Let it happen: Move, assign, comment, create a card or an incident, post to Discord, Slack or Teams, or call your own URL.

What automation and the API include.

• Fifty triggers. Cards, checklists, due dates, GitHub, errors and spikes, incidents, releases, meetings, feedback, goals, polls and incoming web requests.
• Scheduled rules. Every day, week or month, at the hour you choose.
• Buttons. A button on a card or at the top of the board runs a whole series of steps.
• Due-date rules. A notification a day before the deadline, or an overdue card moved to another list.
• REST API. Cards, lists, sprints, docs, time, incidents, releases and more, with keys per workspace.
• Webhooks. Over fifty events, signed with HMAC-SHA256, with example payloads and a test button.
• MCP server. 95 tools for Claude, Cursor or another assistant: cards, sprints, docs, incidents, retros and more.
• Incoming web requests. A rule with its own URL lets your own scripts start an automation.

Frequently asked questions

How many automated actions do I get?

250 a month on Free, 1,000 on Standard and unlimited on Premium.

Which assistants work with the MCP server?

Any client that speaks MCP over HTTP, such as Claude and Cursor. It uses the same keys and permissions as the API.

Can a rule call my own URL?

Yes, on Premium: a rule sends a web request to the URL you choose, with the event’s data.

Where are the docs?

On the API documentation page, with every endpoint, the webhooks and example payloads.

Releases and test runs · Incidents and on-call · Error tracking

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Terms of service · Privacy policy · Error tracking for dev teams, Sentry-compatible · Time tracking and invoicing for dev teams · Status pages with uptime monitoring and incidents · Changelog and release notes from done cards · Incident management and on-call for dev teams · Release management, test runs and DORA metrics for dev teams · Meeting agendas, async stand-ups and retros for dev teams · A feedback portal with voting and a public roadmap · Sprint planning with burndown, a roadmap and OKRs · A Trello alternative for dev teams · A Sentry alternative that keeps your SDKs · A Linear alternative with error and time tracking · A Jira alternative for small dev teams · An Asana alternative for software teams · A ClickUp alternative with error tracking and invoicing · A Toggl alternative with a board and invoicing · A Harvest alternative with a kanban board · A Statuspage alternative with monitoring built in