Release MCP Tools Plugin
Digital.ai Release SaaS includes a built-in Model Context Protocol (MCP) server through the bundled Release MCP Tools Plugin. The MCP server lets AI agents securely interact with releases, templates, tasks, and variables.
The MCP server is enabled by default in Digital.ai Release SaaS. No installation or configuration is required: you can connect an AI agent right away, and Ask Release works without any additional setup.
Connect an AI Agent
To connect an AI client, add the MCP server configuration below to your client's MCP settings. The configuration includes the server URL and the x-release-personal-token header, which authenticates the AI agent with your Release personal access token. The AI agent can access only the resources that your user is permitted to access.
The following example shows an MCP server configuration for the Visual Studio Code mcp.json file:
{
"servers": {
"Digital.ai Release": {
"type": "http",
"url": "https://<your-release-host>/s/mcp",
"headers": {
"x-release-personal-token": "YOUR_PERSONAL_ACCESS_TOKEN"
}
}
}
}
The MCP server URL is your Release server base URL followed by /s/mcp, for example https://release.example.com/s/mcp.
For Cursor and Claude Code, use the same x-release-personal-token header. For Claude Desktop, pass it on the command line as --header x-release-personal-token: YOUR_PERSONAL_ACCESS_TOKEN.
Replace the placeholder values with your Release server URL and your personal access token.
Available Tools
The plugin provides the following tools, grouped into read-only tools and read/write tools.
Read-only Tools
| Tool | Description |
|---|---|
list_releases | List and filter releases, active or archived. |
get_release | Get the details of a release. |
count_releases | Count releases that match a filter. |
download_attachment | Download a file attached to a task or release. |
list_templates | List templates across folders. |
get_template | Get a template, including its phases and tasks. |
list_folders | Browse the folder hierarchy. |
find_folder | Find a folder by its path. |
search_configurations | Search configurations by type and title. |
get_configuration | Get a configuration. |
list_variables | List variables in a release, template, folder, or global context. |
get_variable | Get a variable. |
get_type_names | List the available object types. |
get_metadata_type | Get the definition and properties of a type. |
get_activity_logs | Get the activity log of a release. |
list_installed_plugins | List installed plugins and their versions. |
search_available_plugins | Search the plugin gallery for available plugins and updates. |
list_triggers | List release triggers. |
get_trigger | Get a trigger. |
Read/Write Tools
| Tool | Description |
|---|---|
create_release_from_template | Create a release from a template. |
start_release | Start a release. |
manage_template | Create, update, or delete a template. |
manage_folder | Create, delete, or move a folder. |
manage_configuration | Create, update, or delete a configuration. |
manage_variable | Create, update, or delete a variable in any context. |
manage_phase | Create, update, or delete a phase. |
manage_task | Create, update, delete, or change the type of a task. |
transition_task | Complete, fail, retry, skip, or abort a task. |
manage_gate_condition | Create, update, or delete a gate condition. |
manage_gate_dependency | Create or delete a gate dependency. |