Use case · Bots, apps and agents

The task backend behind your bot

Your Slack bot, internal app or AI agent creates and updates tasks in Taskavel over MCP. Webhooks tell it when a task moves or is done, and your team sees everything on the board.

MCP https://taskavel.com/mcp/taskavel

Your bot writes tasks over MCP

Point your bot at https://taskavel.com/mcp/taskavel with a personal access token. With 70 typed tools it can create tasks, move them between columns, assign people, set due dates, comment and log time.

Webhooks report back

Subscribe an HTTPS endpoint to task.created, task.updated, task.moved, task.completed and task.archived for a project or a single board. Each subscription has its own signing secret, and failed deliveries can be redriven.

Your team hears about it in chat

Project integrations post task activity to Slack, Discord and Telegram, so people who never open the board still see what changed.

Planned

REST API

MCP is how you integrate today. A REST API is coming soon.

Planned

AI users

Soon an agent will be able to join your team as its own user. Today it works through the account whose token it uses.

A customer’s team runs a Slack bot on Taskavel: requests from chat become tasks on the board, and the bot reports back when they are done.

  1. 1 Create a project and a board in Taskavel for the work your bot handles.
  2. 2 In Account Settings → AI Integration (MCP), create a personal access token named after the bot.
  3. 3 Add the Taskavel MCP server to your bot and send the token as a Bearer header.
  4. 4 Add a webhook for the board and, if you want, connect Slack, Discord or Telegram notifications in the project settings.
How does a bot create tasks in Taskavel?

It calls the Taskavel MCP server at https://taskavel.com/mcp/taskavel with a personal access token. The task tools create, update and move tasks, with details such as assignee, due date and priority.

Which events do webhooks send?

task.created, task.updated, task.moved, task.completed and task.archived, for a whole project or a single board. Each subscription has its own signing secret, and failed deliveries can be redriven.

Can the team get Slack, Discord or Telegram notifications?

Yes. Connect Slack, Discord or Telegram in the project’s integrations, and task activity is posted to that channel.

Do I need a REST API?

No. MCP is the integration today, and any client that can call a remote MCP server over HTTP can use it. A REST API is coming soon.

How are tokens scoped?

A personal access token acts as the Taskavel user who created it. It can only reach that user’s projects, within that user’s role. Create one named token per bot and revoke it in AI Integration (MCP) when you retire the bot.

Simplify Your Workflow - Start Today!

Eliminate the hassle and streamline every step of your workflow. Our platform helps you manage tasks effortlessly, collaborate better, and stay focused on what matters most. Start today and experience a smoother, more productive way of working.

Explore Features