Tricentis Tosca Cloud MCP — space automation
Automate Tosca Cloud through the hosted HTTP MCP server at https://{tenant}.my.tricentis.com/{spaceId}/_mcp/api/mcp. Requires a connected tenant with valid Okta bearer token and configured spaceId.
MCP tool names: bare names (tosca_inventory_search) when Tosca Cloud is the only MCP server; tosca-cloud:tosca_inventory_search when multiple servers are connected.
Session checklist
Copy and track progress:
Tosca Cloud MCP session:
- [ ] Readiness — when-to-use-mcp.md; tosca_organization_listWorkspaces succeeds
- [ ] Mode — code-mode.md OR direct-tool-mode.md
- [ ] Intent doc — tool / space / playlist / builder / di orchestration (one only)
- [ ] Plan — script or numbered tool table before first mutation
- [ ] Execute — search before mutate; explicit entityIds
- [ ] Verify — re-read artifact or run status after mutations
Conditional routing
| User goal | Read first | Then |
|---|---|---|
| Is MCP appropriate? | when-to-use-mcp.md | Classify intent below |
| Read-only / audit | tool-orchestration.md | tosca_inventory_search → inspect |
| Edit artifacts / folders | inventory-orchestration.md | Search → mutate |
| Playlist / execution | playlist-orchestration.md | Search → run → poll |
| Execution logs / run detail | execution-orchestration.md | Recent runs → log tools |
| Builder / test cases | builder-orchestration.md | Search → scaffold/edit |
| Mobile connections | mobile-orchestration.md | List → create/update |
| API execution connections | apiexecution-orchestration.md | List → create/update |
| API simulation deploy | simulation-orchestration.md | Deploy → verify agent |
| Data Integrity | di-orchestration.md | One DI reference file below |
| Tester journey (analyze, author, explain) | Journey skills — see repo AGENTS.md |
Pick one journey skill |
Execution modes
| Mode | When | Document |
|---|---|---|
| Code Mode (preferred) | IDE has code execution / programmatic MCP | code-mode.md |
| Direct tool mode (fallback) | MCP tools only, one call per turn | direct-tool-mode.md |
Workflow templates (pick one)
| Workflow | File |
|---|---|
| Connect tenant | reference/workflows/connect-tenant.md |
| Inspect space | reference/workflows/inspect-space.md |
| Search artifacts | reference/workflows/search-artifacts.md |
| Manage folder | reference/workflows/manage-folder.md |
| Create playlist | reference/workflows/create-playlist.md |
| Run playlist | reference/workflows/run-playlist.md |
| Analyze run failures | reference/workflows/analyze-run-failures.md |
| Rename playlist items | reference/workflows/rename-playlist-items.md |
| Scaffold test case | reference/workflows/scaffold-test-case.md |
| Manage API message | reference/workflows/manage-api-message.md |
| Data Integrity intro | reference/workflows/di-getting-started.md |
| DI DB Expert testcase | reference/workflows/di-db-expert-testcase.md |
| Mobile connection | reference/workflows/mobile-connection.md |
| API execution connection | reference/workflows/api-execution-connection.md |
| Deploy simulation | reference/workflows/deploy-simulation.md |
Data Integrity reference (pick one)
Load di-orchestration.md first, then one file:
| Scenario | File |
|---|---|
| Index / router | reference/di/index.md |
| Overview | reference/di/overview.md |
| Conventions | reference/di/conventions.md |
| Row-by-row comparison | reference/di/workflows/01-row-by-row-comparison.md |
| File comparison | reference/di/workflows/02-file-comparison.md |
| DB Expert testcase | reference/workflows/di-db-expert-testcase.md |
Tool reference (on demand)
| Resource | Purpose |
|---|---|
| reference/tools-catalog.md | Tool names and parameters (generated) |
| reference/tools-index.md | Quick tool lookup by domain |
| reference/workflows-index.md | Workflow template index |
| tool-planning.md | Planning primitives |
Prerequisites
| Requirement | Notes |
|---|---|
| Tosca Cloud tenant | https://{tenant}.my.tricentis.com (production) |
| MCP connected | User configured tenant in IDE Settings → MCP |
| Space configured | spaceId in MCP URL path |
| Entitlements | Some tools require product entitlements |
When MCP is unavailable
Use the Tosca Cloud portal UI or REST APIs directly.
Journey skills (tester workflows)
For analyze / remediate / author / explain journeys, use the PM journey skills in this repo — see root AGENTS.md. Engineering skill handles tool orchestration; journey skills handle user-story workflows.