What your AI can do with Loam

One shared resource, one selected account

Add Loam's configured MCP URL to your AI tool. During OAuth, choose exactly one workspace-qualified account: My account or an eligible Agent. That choice stays fixed for the authorization.

Permissions are checked live

Loam evaluates the selected account's current direct permissions, permitted group permissions, denies, capabilities, and MCP restrictions on every request. OAuth tokens identify the account and authorization; they do not contain a copied permission snapshot.

When an Agent is selected, the Agent's authority applies. The related human's personal or group data access is never combined with it. If the Agent loses access, or the human loses permission to use that Agent, the next request fails or narrows immediately.

Query results go to your AI tool

A connected tool can list permitted data, inspect permitted schemas, and run the MCP operations shown on the consent screen. Query results are returned to that tool, so select the least-privileged account suitable for the work.

Read/write is the default and remains least-privileged

New connections default to mcp:read mcp:write, and the consent screen shows that the client can view and update data before you approve it. Loam starts with the selected account's current data access, preserving Data admin when that account already has it. You can narrow the connection to Viewer, Editor, specific data, or exclusions; a client can also explicitly request read-only mcp:read. Write scope and a Data admin ceiling never create a permission: Loam still checks the selected account's live seat, workspace, grants, capabilities, ceilings, and denies for every call.

The execute_sql_query tool remains read-only. The separate execute_sql_mutation tool can run exactly one permitted row insert, update, or delete; create a Namespace; or create, alter, or drop one Table. It cannot switch workspaces, manage grants, bypass a deny, or change system-owned integration Tables. Select the least-privileged account and consent only to the scope the work needs.

Row mutation operation keys support safe equivalent retries. Table schema operation keys are only audit correlation. After an uncertain schema result, your AI must inspect the catalog and Table schema before deciding whether another change is needed.

Each human authorization is independent

Alice and Bob can both connect the same client to the same Agent through the same Loam MCP resource. Their authorizations, refresh families, and audit provenance remain separate. Revoking Alice's connection does not revoke Bob's.

Review live access and revoke individual connections in Settings > Connect AI (sign in to open this page).