Connect Cursor to your BoxOwl vault
Cursor is MCP-native. @boxowl/skills writes the right config into ~/.cursor/mcp.json; you restart Cursor and you're done.
Step 1 — Create an agent token
In the BoxOwl Android app:
Settings → AI Agent Connections → New.
Suggested name "Cursor on <machine>"; starter scopes
vault:read, profile:read, agent:query.
Copy the plaintext token (shown exactly once).
Step 2 — Install the local daemon
brew install boxowl/tap/boxowl-daemon
Or download a binary from github.com/BoxOwl-Me/daemon/releases.
Step 3 — Run the skills installer
npx @boxowl/skills add --platform=cursor --token=bxusr_…
Writes the boxowl entry into
~/.cursor/mcp.json under the top-level
mcpServers key. The installer detects Cursor by
looking for cursor in your PATH or the
~/.cursor/ directory.
Step 4 — Restart Cursor
Quit and reopen Cursor (Cmd+Q on macOS; closing the window doesn't
cycle MCP servers). On reopen, the new boxowl tools
appear in Cursor's agent surface.
Step 5 — Test a query
Open Cursor's chat and ask:
What email is on my BoxOwl vault?
Cursor calls boxowl_get_item identity.email through
the MCP server, the daemon decrypts the row locally, and you get
the answer inline. Writes (saving credentials, updating contact
info) gate behind a confirmation prompt by default — see
Agent tokens for the scope
+ confirmation-mode vocabulary.
Remove the connection
npx @boxowl/skills remove --platform=cursor
Strips the entry from ~/.cursor/mcp.json; sibling MCP
servers are untouched. Revoke the underlying BoxOwl agent token
from Settings → AI Agent Connections in the
BoxOwl app if you want it gone server-side as well.