MCP capabilities enhancements

App Feedback
,
1

Hi,

the MCP connector for Claude desktop is great and helpful with test creation. There is one issue that I come across and it would be amazing to enhance.

Once the test cases are created in Testiny, Claude is unable to make any edits. I can understand the limitation for deleting tests, however, having the ability to update them would be very useful. If there are any changes to the requirements or to the app, Claude can only create new tests, so I would have to go and delete the old ones (not always ideal) or make the adjustments manually.

Are there any plan to add some additional capabilities for the MCP?

Thanks,

Matej

EDIT: I was also trying to get the linked bugs, but that is not available for the MCP as well. That would also be quite helpful.

MCP for Testiny server
2

Thanks for your feedback! I totally understand the need for editing test cases via MCP :+1:

There are already some requests to extend the Testiny MCP server. We will try to take them into account for the next update to the MCP server.

Please, add your ideas for the MCP server as a post to this topic!

If somebody reads this request and also would like to have this feature, make sure to vote for this topic. We do consider the number of votes for feature requests in our roadmap and priority planning.

Best regards,
Alex

3

We’re using Testiny’s MCP integration with Claude and we need the following additional endpoints to automate our workflow:

  1. createProject — Create new projects with key, name, description, and custom field definitions

  2. createTestCaseFolder — Create folders and subfolders within a project (with parent folder support)

  3. Date/time metadata in responses — Include created_at and updated_at fields in listTestCases, listTestRuns, and test result responses so we can track when bugs were opened and when test cases were written

  4. Date-based filtering / aggregation — Ability to filter test cases or results by date range (e.g., “test cases created between 2026-04-01 and 2026-04-15”) to generate productivity metrics

These would allow us to fully manage our test infrastructure through Claude without switching to the Testiny UI.

4

One note for everyone needing detailed data already now which might not be available through the MCP server, yet:

You can also interface with Testiny using the Testiny API, see the API docs here:

Instead of using the MCP, you can also let your AI interface with the Testiny API. We recommend using explicitly generated API keys for accessing the API:

Thank you!

Best regards,
Alex

5

Tried the MCP connector with VS Code (Copilot). Really great and helpful with test creation.
But currently it does not have the ability to link JIRA issues to the test cases’ Requirements tab while creating test cases. Would be really helpful if that can also be implemented.

Requests:

  • Linking of JIRA issues to the Requirements tab of a TC (IMP)

  • Filtering/Searching for all/specific linked Requirements in a given project (IMP)

  • Filtering user list with respect to roles (admin)

  • Finding total active/inactive users (admin)

  • Finding users by “last login” data (admin)

6

Hi all,

if I may jump in and also add to the request the ability to create links between ClickUp issues and Testiny. Once the MCP Server creates a ticket for a defect, it can only add the URL as a comment to the test run, but not link it under the defect tab.

Thanks!