# Loop — how to connect

Voice-first operator for the agents you already pay for. Mac app. You talk. Loop briefs, dispatches, and talks back into your chats.

App:
https://get-loop.ai/

Connect sheet (this file):
https://get-loop.ai/mcp.txt

Longer note:
https://github.com/sledgeworks/loop (private) → docs/CONNECT.md

There is no public Loop MCP URL. Loop is local.

## Two jobs

1. Connect tools *inside* Loop (Cursor, Claude Code, Codex, Knock Knock) — Settings → Integrations after you install the app.
2. Connect *this* AI *to* Loop — inbound CLI. Loop.app must be running.

## Install

1. Download https://get-loop.ai/ (macOS DMG)
2. Open Loop
3. Settings → Integrations
4. Connect Cursor (browser login). Connect Claude / Codex if you use those arms.

Connected means this Loop account linked the tool. Leftover `gh auth` or `.env` on the Mac does not count.

## Cursor / Claude Code / Codex (inside Loop)

Those hosts are execution arms. Loop holds the speech token. The arm holds Linear/GitHub/MCP the way you already set it up.

Cloud Agents do not inherit this Mac's `~/.cursor/mcp.json`. Knock Knock is the bus they report on. Sheet: https://get-knockknock.com/mcp.txt

## Inbound CLI

Spark-shaped. The running app is the authority.

```
ln -sf ~/code-repos/loop/bin/loop ~/.local/bin/loop
# packaged: /Applications/Loop.app/Contents/Resources/bin/loop

loop chats
loop chat <id>
loop brief
loop send <id> "..."
loop skill
```

Loop.app must be open. Do not invent a Loop HTTP MCP server.

## First thing to try

Open Loop. Then: loop chats

## Agent paste-prompt

Read https://get-loop.ai/mcp.txt. Do not add a Loop HTTP MCP. If the user wants tools connected, tell them Settings → Integrations in the app. If they want this chat to drive Loop, install `loop`, confirm Loop.app is running, then `loop chats`.

## Not this

Granova https://granova.ai/mcp.txt
Chive https://usechive.com/mcp.txt
Knock Knock https://get-knockknock.com/mcp.txt
Levered Alex https://levered.marketing/mcp.txt
The Levered work-loop skill is not Loop.