Connect an agent

Use a client that supports a remote MCP server over Streamable HTTP and the server’s authorization requirements.

Server address


https://api.infralane.cloud/mcp

Configure this as the remote MCP endpoint, not as a normal website to open in a browser. An unauthenticated request receives an authorization challenge. A browser showing an authorization error at this address does not establish whether the server is healthy.

Browser authorization

Add the remote server address using your client’s MCP configuration interface.
Start its authorization flow. The client discovers the protected-resource and OAuth authorization-server metadata.
Sign in to Infralane, completing MFA if enabled.
Review the client name and callback address. Client-supplied names are not verified identity claims.
Select projects, permissions and an access expiry, or decline the request.
Return to the client and ask it to inspect the selected project.

An authorization-capable client needs authorization-code OAuth, S256 PKCE and resource binding. Dynamic registration is available for supported public clients; administrators can also pre-register clients. Client-specific menus and syntax differ, so this guide describes the shared contract rather than an untested one-click setup.

Initial authorization requests read access. A workflow may require additional permission. A compatible client can reopen consent when the server responds with an insufficient-scope challenge. You can decline the additional request.

Headless or manually configured clients

Account settings → Agents can create an expiring, project-scoped token when a client cannot complete browser authorization. Review the available permissions and selected projects before creating it. The token is available only once.

Configure the token in the client’s secure authorization-header settings:


Authorization: Bearer <your agent token>

Do not paste the token into a prompt, source repository, server URL, screenshot or support message. Do not use a normal dashboard session token for MCP authentication. A manually created token cannot expand its own permissions; create a new token with the required scope if necessary.

Manage the connection

Open account settings → Agents to inspect projects, scope, expiry and last use, or revoke a connection. Revocation stops future access and can prevent queued work from submitting. It cannot undo a deployment that has already been submitted.

Continue with Permissions and access, Deploy through MCP, or Troubleshooting.