This file is for a coding agent asked to set Loom up as an MCP server for its user. People can read the README and the quickstart. Claude Code and Codex have their own setup contract: agent-setup.txt.
Loom runs on the user's machine as a Docker Compose stack (the Loom server, its document
extractor and ClickHouse) and serves MCP over streamable HTTP. A coding agent connects on
http://localhost:7777/mcp?toolset=coding. Loom needs no API key and no account.
Do not use sudo, install or upgrade system packages, or change Docker's setup. When a
command fails, or a step below says to stop, stop and show the user the command's last
lines.
On Windows, run the curl, docker and env commands, the ~/.loom check and the
installer in a WSL 2 terminal where docker works. Cline on Windows keeps its
configuration on Windows: write the step 3 entry there, and run cline mcp add where
Cline runs, not inside WSL.
curl -sS --noproxy '*' --max-time 5 http://localhost:7777/v1/health- A JSON reply with a
schema_versionfield is a Loom server. If itsstatusisok, go to step 3. Otherwise stop and show the reply to the user. - If no Loom answers (no reply, or one without
schema_version) but~/.loom/compose.yamlexists, stop and ask the user: an install is there that is stopped or runs on another port (LOOM_PORTin~/.loom/.env), and running the installer again would start or upgrade it.
Docker with the Compose plugin, version 2.20 or later, must be installed
(docker compose version). If that command fails or reports an older version, stop.
The installer reads LOOM_* environment variables, which can point it at another
ClickHouse, port or directory. If env | grep '^LOOM_' prints any, stop and ask the user
whether to keep them.
The command runs the installer from the user's home directory:
cd ~ && curl -fsSL https://github.com/ClickHouse/loom/releases/latest/download/install.sh -o loom-install.sh && LOOM_CONNECT=none LOOM_LOCAL_MODELS=off sh loom-install.sh && rm loom-install.shLOOM_CONNECT=nonestops the installer from setting up other agents, since you add the MCP entry yourself in step 3.LOOM_LOCAL_MODELS=offstops it asking whether to run Loom's models on an Ollama it finds, a question that would wait for an answer; ask the user, and passLOOM_LOCAL_MODELS=ollamainstead if they want that.- The installer verifies the release bundle, pulls the images and waits until
/v1/healthanswers. The first run takes a few minutes. - When it finishes, it prints
Dashboard: http://<host>:<port>/. If that port is not7777, replace7777with it in every command and entry below. - If it says port
7777is in use, run the command again with theLOOM_PORT=…its message names in front ofsh. - The install lives in
~/.loom;LOOM_INSTALL_DIRchooses another directory.
Add a loom entry under mcpServers and keep every other entry in the file. If a loom
entry is there already, ask the user before changing it.
The stock install is single-user: it has no sign-in and needs no token. To check, list the tools without one:
curl -s --noproxy '*' --max-time 5 -o /dev/null -w '%{http_code}\n' -X POST 'http://localhost:7777/mcp?toolset=coding' -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'200 means no token is needed. 401 means sign-in is on: ask the user for a token from
Settings → Tokens in the dashboard. Add it as a headers entry,
"Authorization": "Bearer <token>", beside url in the entry below, or with
--header "Authorization: Bearer <token>" on the cline mcp add command. A 401 on a
later tool call, in step 4, means the same: ask for a token and add it.
The Cline extension: its settings file opens from MCP Servers → Configure MCP Servers
in Cline; on Linux it is
~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json.
The entry:
{
"mcpServers": {
"loom": {
"type": "streamableHttp",
"url": "http://localhost:7777/mcp?toolset=coding"
}
}
}The Cline CLI: run
cline mcp add loom 'http://localhost:7777/mcp?toolset=coding' --transport http --yes, or
add this entry to ~/.cline/data/settings/cline_mcp_settings.json:
{
"mcpServers": {
"loom": {
"transport": {
"type": "streamableHttp",
"url": "http://localhost:7777/mcp?toolset=coding"
}
}
}
}The MCP clients page gives the entry for other clients.
- Reload the MCP servers (the Cline CLI loads them when a session starts, so start a new
one). The tool list includes
loom_memory_setandloom_search. - Pick a key
setup/check/<random digits>and callloom_memory_geton it. If it is found, pick another key. - Call
loom_memory_setwith thatmemory_keyand a shortvaluethat contains the same digits, thenloom_memory_getwith the same key: it returns the value. - Call
loom_memory_deletewith that key. - Tell the user where the dashboard is: the
Dashboard:address the installer printed, orhttp://localhost:7777/when Loom was already running.
The code tools (loom_code_search, loom_code_symbol and the others) answer once a
repository is indexed. On the released stack, add it to LOOM_CODE_REPOS_JSON
(Index a repository).