When to contact your administrator

Your administrator handles pending users, unavailable services, permission changes, account service failures, reviewer settings, and persistent 503 errors. Start with Troubleshooting.

Generate a diagnostic report

mcpbridge doctor --profile work --client ci_example --json --timeout 30s > mcphub-diagnostics.json

Use the actual entry ID. The report does not include tokens or process communication credentials. Blocking problems return a nonzero exit status, but the report already written is retained.

Include details that help locate the problem

  • Time, timezone, and frequency.
  • Operating system, CPU architecture, CLI version, and AI client version.
  • MCPHub URL, profile, entry ID, service, and tool.
  • The exact error, diagnostics, request ID, or approval ID.
  • Expected and actual results, and any recent reauthorization, account replacement, or upgrade.

For a write, state whether it was not executed, was accepted, or has an uncertain result. Verify the result before retrying.

Copyable issue template

Problem:
Time and timezone:
Operating system / CPU architecture:
mcpbridge version:
AI client and version:
MCPHub URL:
Profile / client ID:
Endpoint / tool:
Request ID / approval ID:
Steps:
Expected result:
Actual error:
Write execution status or uncertainty:
Recent changes:
Attachment: mcphub-diagnostics.json

Review before sending

Do not send credential directories, login tokens, personal tokens, complete authorization URLs, or active pairing codes. Handle business identifiers and parameters according to company policy. Your administrator can look up the event using its time and request ID.

Report a product issue

Contact your internal administrator first for company access or business problems. Once a product defect is confirmed, your administrator can submit a reproduction without secrets to GitHub Issues. Follow the security reporting instructions for security issues.