MCP troubleshooting — Altifigence Documentation

Cannot connect a hosted client

Check that the configured URL is https://mcp.altifigence.com/cloud-mcp and that the client supports Streamable HTTP with OAuth. Follow connection guidance and the current qualification status. The server’s health page and OAuth metadata do not prove that a particular client has completed authorization.

Result	Next step
HTTP 401	Reconnect Altifigence Cloud if authorization expired or was revoked; complete the client authorization flow again
HTTP 403	Check the consented organization, current project access and tool policy; reconnect with the required permission after the organization enables the tool
Empty or missing tools	Check the released catalog, explicit organization approval and fresh consent for each tool; refreshing an old token cannot add tools
Workspace read unavailable	Check workspace status and access in Cloud; retry after it is ready
Execution tools missing	Request fresh `cloud.execute` consent and check release, organization policy and project runtime access
Write tools missing	Request fresh `cloud.write` consent and check the organization’s explicit tool and project permissions
File mutation conflict	Read the manifest and file again, review concurrent changes, then submit the intended change with current revisions
Project creation or Git mutation not confirmed	Inspect the project list, repository or remote state before retrying; a repeated create, commit or push can have unintended effects
Project deletion accepted	Follow project/workspace state until cleanup finishes; accepted does not mean complete
Git provider transfer denied	Check the selected repository, branch and current provider connection; the tool cannot bypass provider permissions
Runtime operation not confirmed	Read runtime status and retain the operation ID; resume uses the stopped runtime’s operation ID
Project generation, file version or policy changed	Obtain a fresh estimate and review its selected offer and usage policy
Submission not confirmed	Inspect the same job ID; retry only with identical arguments and that same ID
Result not ready	Read job status before requesting the result again
Insufficient credits	Review the organization’s billing state in Cloud
HTTP 413	Reduce the request to the arguments in the discovered tool schema
HTTP 501 from a local tool	The installed runtime does not implement this operation; discovery alone does not establish support
HTTP 503	Wait for service recovery; keep the configured endpoint

A read request does not start or restart a project. Unknown or unauthorized tool names do not enable editing or execution. Correct the connection or access condition before retrying; do not supply alternative credentials in arguments.

Too many requests

If a response includes HTTP 429, wait for the period specified by Retry-After before trying again. Avoid repeated registration or sign-in attempts.

Contact support

Contact Altifigence Support with the client name, version, time of the problem, and error message after removing sensitive information. Do not include credentials, cookies, or project contents.

Recover without duplicating work

Failure point	Inspect before retrying
Identity or discovery	Client version, endpoint, sign-in/session and consented tool list.
File read continuation	File and manifest versions; restart on a changed snapshot.
File write, commit or push	Current saved file, repository and remote state.
Job submission	The existing job ID and status; retain the original identity.
Terminal input or AI request	Current session/output; do not replay input automatically.

Record the smallest reproducible request with placeholders for project data. Preserve the error code, HTTP status, request identifier if shown, and timestamp. Remove tokens and source contents before sharing a diagnostic.