Agent connection troubleshooting

The endpoint asks for authorization

An unauthenticated MCP request is expected to receive a 401 challenge. Configure the address as a remote MCP server in the client, then complete its supported authorization flow. Opening /mcp as a website is not a connectivity test.

The client cannot authorize

Check that it supports Streamable HTTP, authorization-code OAuth, S256 PKCE and resource binding. Confirm the configured address includes /mcp. Client-specific registration or callback errors require checking the client’s actual configuration. Never bypass certificate warnings or give the agent your account password.

No projects appear

Inspect the selected projects and current connection permissions in account settings → Agents. Confirm your account still has project access. A connection does not automatically see every workspace or project.

A tool requires additional permission

A 403 insufficient-scope response can trigger a new consent flow in a compatible OAuth client. Review the requested permissions. A manual token needs to be recreated with the required scopes; it cannot expand itself.

GitHub repositories are unavailable

Connect GitHub to the project’s workspace in the dashboard. Check the installation is active and can access the desired repository. A public URL alone does not grant the integration access to a private repository.

The agent cannot upload my files

The remote server cannot read a local path. Use the separate HTTPS transfer flow, the human browser handoff, or a GitHub/Docker source. See ZIP uploads.

Build logs require a node upgrade

The MCP build-log snapshot endpoint requires the matching Crane node capability. An explicit upgrade-required response needs infrastructure follow-up; it is not a successful empty log result.

A deployment is failed or ambiguous

Inspect the operation, deployment and bounded log output. Check the same application in the dashboard. Reuse the idempotency key for the same apply operation. Do not blindly submit a new deployment when the earlier submission outcome is unknown.

For help, contact info@infralane.cloud. Include the tool name, error message and relevant non-secret IDs. Remove tokens, environment values, upload tickets and private source from support messages.