> 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/february-2026/february-27-2026.md).

# February 27, 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:

### Hosted MCP v2 — OAuth 2.0 PKCE + Dynamic Client Registration

The hosted MCP server (`https://www.taskade.com/mcp`) was upgraded to the MCP 2025-11 Streamable HTTP transport and now supports full **OAuth 2.0 with PKCE** (Proof Key for Code Exchange, S256 method). Key changes for integrators:

* **Dynamic client registration** — a new endpoint at `POST /oauth2/register` allows MCP clients to self-register without a manual approval step. At launch, redirect URIs are restricted to `claude.ai` domains and localhost (127.0.0.1 / localhost) for CLI clients, as the allow-list is expanded.
* **PKCE-only public clients** — clients registered via `/oauth2/register` are issued as public PKCE clients (`token_endpoint_auth_method: none`, `pkce_required: true`). No client secret is needed.
* **Streamable HTTP sessions** — the MCP endpoint supports session-based Streamable HTTP (`POST /`, `GET /`, `DELETE /`) with per-session state. A `mcp-session-id` header is used to resume sessions.
* **Bearer token auth** — MCP requests authenticate with `Authorization: Bearer <your_pat_or_oauth2_token>`. Personal Access Tokens (PATs) and OAuth2 access tokens are both accepted.

{% hint style="info" %}
The production deployment fix (`fix(mcp): MCP server not connecting on staging/prod`) shipped alongside this release. If you experienced MCP connection failures before Feb 26, retry with the current endpoint.
{% endhint %}

See [Workspace MCP](/developers/workspace-mcp.md) and [Authentication](/developers/authentication.md) for PAT and OAuth2 setup. Source: [github.com/taskade/mcp](https://github.com/taskade/mcp).

***

### New Automation Piece: Telegram Bot

A **Telegram Bot** automation piece is now available, adding 8 actions for sending and managing Telegram messages from automation workflows:

| Action                     | Description                      |
| -------------------------- | -------------------------------- |
| `telegram.sendMessage`     | Send a text message to a chat    |
| `telegram.sendPhoto`       | Send an image via URL or file ID |
| `telegram.sendDocument`    | Send a document/file             |
| `telegram.sendVideo`       | Send a video                     |
| `telegram.editMessageText` | Edit an existing message         |
| `telegram.deleteMessage`   | Delete a message                 |
| `telegram.pinChatMessage`  | Pin a message in a chat          |
| `telegram.getChat`         | Retrieve chat metadata           |

Trigger a Telegram notification from any automation — connect your bot token in the Integrations panel to get started.

{% hint style="info" %}
**Note:** send/manage actions are available at launch; trigger support shipped in a later release.
{% endhint %}

See [Automation Integrations](/automations/automation/integrations.md) for the full integration library and [Integration Kit](https://github.com/taskade/integrations) for the open-source piece source.

***

### Automation: Webhook Signature Mismatch Diagnostics

When an inbound webhook's HMAC signature does not match, automation runs now emit a structured diagnostic log entry instead of a bare rejection. The log includes the expected vs. received signature lengths and the hashing algorithm used, making it easier to debug misconfigured webhook secrets without enabling verbose logging.

See [Webhooks](/developers/webhooks.md) for HMAC signing details.


---

# 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/february-2026/february-27-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.