Extend Testomat MCP by branches support

[vlad-shulika]

Currently, MCP allows creating and updating tests, suites, and other entities, but it is not possible to explicitly specify which Testomat branch the changes should be applied to.

Proposal
Add the ability to pass the branch name in the payload of all MCP operations that work with branch-dependent entities, including:

• tests_create
• tests_update
• tests_delete
• tests_get
• tests_list / tests_search
• suites_update
• other related methods, if they also depend on branch context

Additionally, add branch capabilities, at minimum:

• branches_list — get the list of project branches
• branches_create — create a new branch
• branches_exists — check whether a branch exists

Expected Behavior

• If branch is provided in the request, the operation must be executed in the context of that branch.
• If branch is not provided, the current default behavior should be preserved.
• This should work consistently for both read and write operations, so it is possible to both read and modify data within a specific branch.

[AenEnlil]

@DenysKuchma Be done

[mykhailiukVitalii]

I installed the latest Enterprise MCP version (2.2.0-beta.4) and tested a couple of requests.

I can confirm that the tools for branches flow are available in this version:

• testomat_mcp_branches_list - List project branches
• testomat_mcp_branches_get- Get branch by slug
• testomat_mcp_branches_create - Create branch
• testomat_mcp_branches_update - Update branch
• testomat_mcp_branches_delete - Delete branch

And user via MCP has access to this new options:
Example-1: Create a new branch via MCP- prompt: As you have option to create testomat_mcp_branches_create - create a new branch "develop" with at least one test

Example-2: Get branch by slug - prompt: Use testomat_mcp_branches_get show the list of all available branches in my project

Status ✅ - Based on the list of "branch" options, I can confirm that user can create, update, get list of existing branches.
@TetianaKhomenko FYI