MCP authentication and connections

Use https://mcp.atmina.ai/mcp for authenticated Team memory. Your client discovers the authorization service, opens a browser, and asks you to approve a delegated connection. Sign in as the person whose access the client should use.

The connection receives coarse read or write scope, then Atmina applies your live Team and Knowledge Base access to every request. A token does not grant access that its responsible user has lost.

If authorization is interrupted, return to the client and retry its connect action. Clients that support device authorization show a short code and verification address. Open that address, sign in, and check that the code, client and requested access match the connection you started. Choose Allow to continue or Deny to refuse it, then return to the client. If the code has expired, start again from the client.

For a device connection, approval is followed by activation in the client. Wait for the client to confirm the connection is ready; a pending connection cannot yet read or write Team memory. Browser-authorized connections are active immediately. Client developers can find the activation and revocation operations in the REST Agent Contract.

Reconnect older clients when Atmina says their authorization generation is no longer current.

Review and revoke connections under Account → MCP connections. Never paste an access or refresh token into a support request. See connect your agent for the everyday setup and MCP Memory Tools for available operations.