Connect Birdtask with MCP

Use Birdtask’s remote MCP server to view and organize your boards and tasks from a client that supports Streamable HTTP.

Create a personal token

1. Sign in and open Settings → Integrations.
2. Name the token. Leave write access off for queries; enable it if the client needs to change boards or tasks.
3. Create and copy the token immediately. The full value is shown only once.

Sign in to Birdtask

Configure your MCP client

Choose Streamable HTTP and send the token in the Authorization header of every request.

Endpoint: https://birdtask.com/mcp

Authentication: Authorization: Bearer <BIRDTASK_TOKEN>

Generic configuration example; the exact format depends on your client:

{
  "mcpServers": {
    "birdtask": {
      "url": "https://birdtask.com/mcp",
      "transport": "streamable-http",
      "headers": {
        "Authorization": "Bearer ${BIRDTASK_TOKEN}"
      }
    }
  }
}

Replace BIRDTASK_TOKEN with your generated token. If your client does not expand environment variables in this field, configure the header as its documentation describes. Never commit the token to a repository.

Available tools

Read tools are available to every token. Write tools require a token created with write access.

Read

list_boards, get_board, list_tasks, get_task, list_today_tasks.

Write

create_board, update_board, archive_board, create_task, update_task, set_task_completed, move_task, postpone_task, delete_task.

list_today_tasks includes tasks due today and tasks marked as immediate, using your account’s timezone.

Access and security

Tokens expire after 90 days and can be revoked in Settings → Integrations. Treat them like passwords and use a separate token for each client.

A client can access only boards and tasks available to your account. Write operations remain subject to your permissions on each board.