Skip to content

Tricentis/mcp-skills / Tosca/Cloud/MCP/claude/skills/tosca-cloud-connect

tosca-cloud-connect

Verified

Verifies hosted Tosca Cloud MCP connectivity and routes to the right Cloud skills. Use when the user is setting up Cloud MCP, fixing 401 errors, or before other Tosca Cloud skills. Does NOT configure MCP servers — the user adds their tenant in the host (IDE settings or Copilot CLI `copilot mcp add`).

Connect Tosca Cloud MCP

This skill pack installs agent skills only. Connecting to Tosca Cloud MCP works like any IDE plugin: the user (or IT) adds their tenant server in Settings → MCP. The IDE handles authentication on first use.

Hosted endpoint (user-supplied)

Production URL pattern:

https://{tenant}.my.tricentis.com/{spaceId}/_mcp/api/mcp
EnvironmentHost pattern
Production (default){tenant}.my.tricentis.com
Staging{tenant}.my-test.tricentis.com
Internal dev{tenant}.my-dev.tricentis.com

tenant is the slug from the Tosca Cloud portal (acme from https://acme.my.tricentis.com). Confirm spaceId with the user (often default).

Setup checklist

Connect Tosca Cloud MCP:
- [ ] Skills installed (marketplace plugin, zip/git installer, or manual copy)
- [ ] User added MCP server (IDE settings or Copilot CLI `copilot mcp add`) with their tenant URL
- [ ] User completed browser sign-in when IDE prompted
- [ ] Verify: tosca_module Search
- [ ] Load tosca-cloud-basics, then task-specific skill

Configure MCP (user action)

Do not run scripts to generate MCP config on the user's machine unless IT explicitly requires it — this pack does not ship connection automation.

Cursor

  1. Settings → MCP → Add server (or edit an existing Tosca Cloud entry).
  2. Set the server URL to the tenant pattern above (include spaceId in the path).
  3. Reload Cursor if needed.
  4. On first connect, complete Okta / SSO in the browser when the IDE opens it.

Claude Code

  1. Add the same tenant URL in Claude Code MCP settings.
  2. Reload Claude Code; complete sign-in when prompted.

GitHub Copilot CLI

  1. copilot mcp add --transport http tosca-cloud "https://{tenant}.my.tricentis.com/{spaceId}/_mcp/api/mcp"
  2. Start copilot. If the server shows needs-auth, run /mcp auth tosca-cloud.
  3. Confirm skills with copilot skill list or /skills info tosca-cloud-connect.

Copilot CLI reads ~/.copilot/mcp-config.json (mcpServers). It does not read .vscode/mcp.json.

VS Code Copilot Chat

  1. Command Palette → MCP: Add Server (HTTP) with the tenant URL.
  2. Reload the window; complete Okta sign-in when prompted.

Personal skills live in ~/.copilot/skills (shared with Copilot CLI). Workspace skills live in .github/skills.

Verify connectivity

After the user connects in IDE settings:

tosca_module Search
ResultAction
Search result returnedProceed — load tosca-cloud-basics or task skill
401 / unauthorizedUser re-authenticates via Settings → MCP (toggle off/on or re-add server)
Connection refusedConfirm URL, space id, network/VPN with user
ErrorConfirm space id with user

Navigating many MCP tools

After connect, do not load the full tool catalog at once.

User goalStart here
First time in Cloudtosca-cloud-basics
Find artifactstosca-cloud-mcp → search-artifacts workflow
Run / diagnose playlisttosca-analyzing-execution-results
Author test casetosca-authoring-manual-testcase or tosca-authoring-automated-testcase
Raw tool order / Code Modetosca-cloud-mcp engineering skill
Data Integritytosca-cloud-mcp → di-orchestration.md, then one DI reference file

Security

  • Never paste JWTs or refresh tokens into chat.
  • OAuth tokens stay in the IDE MCP client — not in this skill pack.
  • Destructive tools still require user confirmation per AGENTS.md.

Troubleshooting

SymptomFix
Wrong tenant in URLUser updates MCP server URL in IDE settings
OAuth failsRetry sign-in from Settings → MCP; check corporate browser/SSO policy
Tools missingCheck product entitlements; some tools are license-gated

Related

  • tosca-cloud-mcp/reference/workflows/connect-tenant.md — step-by-step for agents
  • tosca-cloud-mcp/when-to-use-mcp.md — readiness after connect
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall