Skip to main content

​
Troubleshooting

Every generated server is scanned before deploy. If a build is blocked:
  • Check the build log for the flagged rule and file.
  • Generated output must avoid eval() and dynamic imports — if a custom edit introduced one, remove it.
  • Re-run the build after the offending pattern is gone.
  • Confirm status first: mcp deployments get <deploymentId>.
  • Tail events: mcp deployments logs <deploymentId> --follow --since 1h.
  • In CI, bound the wait: mcp --json deployments logs $ID --follow --follow-timeout 300.
  • Verify you’re querying the correct deployment id and organization scope.
  • Verify MCPCLOUD_API_KEY is present and not revoked (mcp whoami).
  • Confirm the caller has the required org capability (billing/audit routes are capability-gated to admin/owner).
  • Re-check organizationId and resource ids in the query or body.
  • Include both deploymentId and organizationId in the exchange.
  • Confirm the deployment’s access mode and runtime-auth posture: mcp deployments runtime-auth <deploymentId>.
  • Remember: control-plane API keys are not runtime tokens — see Runtime access.
  • Inspect error.requestId for traceability when filing an issue.
  • Check the transport: most remote clients need Streamable HTTP (the default); some legacy clients need SSE.
  • For privateOrg / unlisted deployments, the client must present a runtime token — a bare URL won’t work.
  • Validate the active endpoint URL from the server workspace.
  • See the per-client Clients guides for exact config.
  • Run enrichment so descriptions are agent-readable: mcp tools enrich <serverId>.
  • Confirm the tool surface is what you expect: mcp tools list <serverId>.
  • Curate out noisy or duplicate operations before re-deploying.
  • Ensure MCPCLOUD_API_KEY is in pipeline secrets (env var takes precedence over config file).
  • CI mode refuses prompts — use --key / MCPCLOUD_API_KEY for login, and --non-interactive for mcp init.
  • Prefer --json + jq for deterministic parsing.
  • Source project/server ids from the current environment, not stale artifacts.
The artifact is monetized. Purchase it, or install a free alternative. Marketplace creators keep 80% of revenue.
Servers, deployments, skills, API keys, and credits are capped per plan and per organization. Upgrade the plan or buy a credit pack on a paid tier. See Credits & plans.

​
Quick diagnostics