There are two cases, and only one of them needs setup.
A local agent needs no setup
Point Claude Code, or any tool that can read your disk, at your vault folder. It edits the .md files directly, the file watcher picks up every change, and it syncs live to your team. There is nothing to configure.
Cloud and autonomous agents use the MCP endpoint
For agents that cannot reach your disk, Baalda exposes a Model Context Protocol endpoint, so any MCP-speaking client can work with your vault exactly like a person, limited by the same per-folder permissions.
- In the app, go to Vault settings, then MCP, and create a token.
- Register the endpoint with your AI client.
claude mcp add --transport http context http://localhost:3010/api/mcp \
--header "Authorization: Bearer mcp_…"On the managed service the endpoint is https://api.baalda.com/api/mcp. On a self-hosted server it is your server URL plus /api/mcp.
What the AI can do
It can read_note, search_notes, create_note, edit_note, a targeted replace, insert or delete at exact anchors, and update_note, among others. Its writes flow through the same sync engine as everyone else's, so if the note is open you will watch the AI type in real time.
read_note returns a revision. Pass it back as expectedRevision and a write against a note that changed in between is refused rather than merged.
Files are in scope too
search_notes ranks text extracted from your documents and spreadsheets alongside your notes, and each hit says whether it is a note or a file. list_attachments lists the files it can reach and read_attachment_text reads the words inside one. All three follow the same per-folder permissions as everything else.
This page is written from README.md in the repository. That document goes further, and it is the one that changes first.