Atlas documentation
Connect an MCP client
Connect Claude, Codex or another MCP client to your Atlas workspace.
Before you connect
Ask your workspace administrator to confirm that MCP access is enabled for your account. Atlas currently gates its MCP door to approved administrators while member access is being validated. A compatible client needs remote HTTP MCP support and the authentication method offered by the server.
Add Atlas
Use https://kindo-five.vercel.app/api/mcp as the current Atlas MCP endpoint. Complete the server's sign-in and consent flow in your client. Do not paste another person's token or integration credentials into a prompt.
Prove the connection
Start with a read-only Atlas tool. Confirm the returned identity and workspace, then inspect the corresponding record in Atlas. A connected badge alone does not prove that a vendor action is authorized.
Connect a system
Add the system through Atlas's connection flow with your own account. Tool discovery and permissions come from that connection. If a service denies an action, resolve its access policy before retrying.