> For the complete documentation index, see [llms.txt](https://docs.taskade.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taskade.com/changelog/changelog-2026/may-2026/may-6-2026.md).

# May 6, 2026

{% hint style="info" %}
**Developer highlights.** This section tracks API, MCP, SDK, automation, and Taskade Genesis platform changes for developers. For the full product changelog see [taskade.com/changelog](https://www.taskade.com/changelog); for release newsletters see [taskade.com/blog/updates](https://www.taskade.com/blog/updates).
{% endhint %}

## What's New:

### `/settings/api` — Centralized API Hub

A new `/settings/api` page consolidates all developer-facing tokens and integrations in one place: Personal Access Tokens (PATs), MCP server setup, CLI access, and API documentation links. Developers no longer need to navigate separate settings screens to manage their API credentials.

### New Automation Triggers: Project Created and Due Date Removed

Two new triggers are available for automation workflows:

* **Project Created** — fires when a new project is added to a workspace or folder, enabling onboarding flows and setup automations.
* **Due Date Removed** — fires when a task's due date is cleared, useful for triggering follow-up actions or reassignments.

### MCP Access for Lifetime-Deal Plans

The Taskade MCP server is now accessible to lifetime-deal plan holders, expanding programmatic agent access beyond paid subscription tiers.

Set up the MCP server: [Workspace MCP](/developers/workspace-mcp.md) ([@taskade/mcp-server](https://github.com/taskade/mcp)).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.taskade.com/changelog/changelog-2026/may-2026/may-6-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.