---
"@type": WebPage
"@id": "https://helloloam.dev/byoa"
"@source": "https://helloloam.dev/data/webpage/byoa.json"
"@stamp": "2026-10-22T21:53:55+00:00"
description: Use the agent you already have — Claude, ChatGPT or any client that speaks MCP.
hasPart:  # 1
  - {"@id":"https://helloloam.dev/data/table/assistants.json"}
identifier: byoa
inLanguage: en
name: Bring your own agent
url: "https://helloloam.dev/byoa"
---

# Bring your own agent

## Full with Claude and Mistral, and works with the rest.

Every assistant can read a loam site. Managing it just by asking works fully in Claude and Mistral today — both connect on any plan, mobile too; the others can too, with a detour. And as the owner you always keep full control on the server, with whatever tool you like.

Loam does not ship an assistant. It gives yours a door: [the MCP](/principles/mcp-with-a-trust-model), with a key per actor and [rights per key](/principles/fine-grained-permissions). Your agent reads the site, [stages changes as drafts](/principles/draft-and-live-lifecycle) and publishes when you say so.

Agents that can use a shell work over SSH and git instead. Either way, every change lands in the journal under the name of whoever made it.