# January 27

## Connectors

### Create more accurate agents with the new Agent Component testing experience

Validating your agents just got a lot easier. You now have an **AI playground integrated into the** [**Agent Component**](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/ai-tools/llm) **settings**. With it, you can test multiple variables simultaneously, allowing you to compare how your Agent reacts to different scenarios in a single run.

This update provides detailed logs on component behavior. This way, you spend less time running complete pipelines and gain more confidence in your Agent's logic before putting it into production. In addition, you can save execution data to keep a performance history at your fingertips.

<figure><img src="/files/e1Lna4lCpC2VNNUALclW" alt=""><figcaption></figcaption></figure>

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/RP4aFzyiDCxoa9hR8NUd" class="button primary">Read the complete documentation</a>

### Scopes: New security control in MCP Server Trigger

Enhance the security of your AI integrations. With the **new scopes feature in** [**MCP Server Trigger**](/documentation/connectors-and-triggers/triggers/web-protocols/mcp-server.md), you can set specific access levels and permissions via JWT Token. This update ensures that your Agents operate strictly under your organization's access rules and policies.

<figure><img src="/files/UU2eZKb782dq4zZK2BSB" alt=""><figcaption></figcaption></figure>

<a href="/spaces/EKM2LD3uNAckQgy1OUyZ/pages/FGD8OOw7DBvy1DCQGwpX#scopes" class="button primary">Learn more</a>

## Platform improvements

### Improved pipeline step search with alias support

We have updated the side panel search to include [**alias**](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/how-to-reference-data-using-double-braces/previous-steps-access) support. Now you can locate existing steps in your pipeline not only by their primary name, but also by their aliases.

This makes navigation more fluid, allowing you to locate steps exactly as they are referenced in your [Double Braces expressions](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/how-to-reference-data-using-double-braces). You gain more agility to manage data and spend less time searching for connectors in extensive flows.

<figure><img src="/files/QiPS8J5hbIHu7GWYC72j" alt=""><figcaption></figcaption></figure>

### Improvements and Bug fixes

#### Improvements

* **`POST` method on the Dynamics 365 connector:** The [Dynamics 365 connector](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/enterprise-applications/dynamics-365) now supports the POST method to create new records.
* **Improved search on Smart Connector feature:** We improved the UX on the search bar for the [Smart Connector feature](https://docs.digibee.com/documentation/developer-guide/development-cycle/build-overview/canvas/smart-connector-user-experience) on Canvas.
* **Streamlined pipeline workflow:** We’ve improved the creation process on the **All Pipelines** page. Now the primary action allows you to jump directly into building pipelines within your default project, removing unnecessary steps.

#### Bugs

* **Different results in searches on Step Library and Smart Connector feature:** We fixed a bug that returned different search results for connectors on both Step Library and Smart Connector on Canvas.
* **Inconsistent ordering in the Project List:** We fixed a bug where the default project changed positions between loads on the Build page.
* **MCP authentication persistence:** We fixed a bug that prevented new MCP accounts and certificates from being saved in existing Agents configurations.


---

# Agent Instructions: 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:

```
GET https://docs.digibee.com/documentation/release-notes/january-2026/january-27.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.