Symptom
The service serves a cert that expires earlier than the one in the source. The jobs look successful.
Fix
Rotate the token as in ↳ INF-20 and run the sync by hand.
kanban with mcp built in
The board your assistant can use
Cards, documents and comments in one place — with an MCP server built in. Your AI assistant creates the cards, moves them and writes the runbook straight into the board, with no integration to build and nothing to copy back and forth.
Free during the beta. Sign in with Google or GitHub.
The assistant works in the board, not beside it
The MCP server lives in the backend behind an API key. Connect it once — then the assistant can read the board, create cards, move them and comment, with the same permissions you gave the key.
- 1Create a key
In Settings → API keys. It is shown once and stored hashed.
- 2Connect it
One line in your assistant. Works with anything that speaks MCP over HTTP.
- 3Ask for something
“File these three bugs and set the first one to in progress.” The cards appear on the board while you watch.
# connect the board to your assistant claude mcp add --transport http tasks \ https://tasks.nu/mcp \ --header "Authorization: Bearer tk_…" # tools that become available list_projects create_issue comment_issue list_issues update_issue get_issue
The rest is a sharp kanban tool
Built to stay open all day: fast, keyboard-friendly and without surfaces you never use.
Board and list
The same cards in two views. Column names, colours, order and visibility are yours to set — per project or as the default for all.
Subtasks across projects
A card can belong to another, even in a different project. The parent shows how many of its children are done.
Search that finds
Press / and type. If nothing matches in the current project, all the others are searched automatically.
Comments in markdown
Write in markdown, paste images straight into the field. Ctrl+Enter sends.
Documents and runbooks
Notes and decisions in the same workspace as the cards, linked to them. With a history of who wrote what.
Open API
Everything the web app does goes through the same REST API, behind keys you create yourself. Build your own integrations without asking anyone.
Feed and log
Everything that happens lands in one feed — who, what and when, whether it came from the web, MCP or an integration.
Your data, exportable
The whole workspace can be downloaded in a format you can read without us. Deletion means deletion.
One workspace per context. Personal, work, the client. Nothing leaks between them.
Every workspace is its own world with its own projects, cards, documents, members, API keys and notifications. You switch with one click at the top of the menu and bring the same account, the same assistant and the same habits. What happens at work stays at work.
Ppersonalowner
The colour is yours to pick — under Settings → Members.
3workspaces on one account
1 clickto switch, no second account
0cards visible across the line
- 1Your first sign-in creates yours
Sign in with Google or GitHub and you are standing in your own workspace. Create more on the spot with “+ New workspace”; a name is all it takes.
- 2Invite with a link
Owner, admin or member, or just chosen projects: the shared person is an admin inside them but sees nothing else in the workspace. The link lasts seven days and the invitee needs a verified email that matches; with an existing account the next sign-in is enough. Colleagues on your domain can request to join and you approve them in the member list.
- 3One assistant, every workspace
An API key normally belongs to one workspace, so the assistant sees only what it should. If you would rather not keep a key per context, tick “Reaches all my workspaces” when you create it: the same MCP connection reaches every workspace with your role in each, and the assistant switches with one tool. It can also create workspaces and invite people for you.
› “Create the card ‘Invoice nordvik’ in the client workspace”
switch_workspace("nordvik") → create_issue(project: "invoices", title: "Invoice nordvik", …)
NOR-14 created · workspace: client: nordvik
Take everything with you whenever you like: export the whole workspace as JSON, and deletion asks you to type the name. A workspace you leave does not disappear for the others.
The part that isn't a task
Cards answer what needs doing. They are bad at how something works and why it ended up this way — that knowledge lands in a comment, in a wiki nobody opens, or in someone's head. Documents live in the same workspace as the cards and link to them.
- ↳The runbook sits on the card
An ops card shows the document that belongs to it. Nobody hunts through another tab in the middle of an incident.
- ↳Decisions stay
Why was this solution chosen? Write it down once, link it from the cards it affects.
- ↳The assistant reads and writes them
The same MCP connection that handles the cards. Ask it to read the runbook before acting, or to summarise a finished project.
Notifications where the team already is
Connect a Discord or Slack webhook per project or for the whole workspace, and choose what to hear about: new cards, status changes, comments. A test button shows right away whether the connection works.
Discord · #tasks
Slack · #ops
Free during the beta
During the beta every workspace has everything in Team, at no cost. This is what the plans will look like once billing arrives: per workspace, not per seat, because the value is in what the assistant does, not in how many people click. When it becomes paid we will say so well in advance, and you can take your data with you.
Free
0 kr/ month
- One workspace for you or a small team
- The MCP server included, with a daily cap
- Documents, boards and folders
- Images up to a limit
- Export and deletion whenever you like
TeamComing soon
Contents and price are not set yet.PlusComing soon
Contents and price are not set yet.EnterpriseComing soon
Contents and price are not set yet.Need help, missing something or found a bug? Say it right where you are.
Support questions, feature requests, design opinions and bugs — all go the same way, from inside the app or by asking your assistant. You follow the report until it is resolved, see when we have answered and can attach images. No form on another site, no inbox to watch.
- 1Write it in 20 seconds
Pick whether it is a question, a request, a design opinion or a bug. A title, a line about what you need, an image if you like. Sent with your name and workspace so we can get back to you — nothing else.
- 2Follow it until it is resolved
Received, looking at it, planned, waiting for you, resolved. Requests we take on get the status planned so you can see it is happening. A mark in the menu when we have replied.
- 3Or ask the assistant
The same MCP connection that handles the cards can ask the question, file the request, list and reply to your reports.
› “Ask the tasks team whether recurring cards every Monday is possible”
report_feedback(kind: "onskemal", title: "Recurring cards every Monday", …)
✓ FB-11 created · status: received
