tricentis-mcp.yml
Tricentis ships remote, product-scoped MCP servers across its quality-engineering platform — Tosca Cloud, Tosca Commander (in-process), qTest and Tricentis Test Management for Jira. Every endpoint is TENANT-SCOPED, so there is no single public MCP URL and tools/list cannot be introspected anonymously (the TTM4J endpoint answers HTTP 401 "Invalid or missing token." to an unauthenticated tools/list). The tool inventories below are the provider's own published lists: the Tosca Cloud registry is harvested verbatim from the Apache-2.0 Tricentis/mcp-skills repository, and the TTM4J list from the Tricentis connection documentation.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.