BrainMop keeps your notes somewhere an AI assistant can read and write them. It does this two ways, neither tied to a single vendor: an MCP server (the Model Context Protocol, an open standard that assistants such as Claude can speak) and a plain REST API. Both use a personal token that you create and can revoke. Keeping and syncing notes is free; connecting an assistant is part of the optional paid plan (see the note at the end).
Open the web app and sign in with an email and password, or with Google. An account is what puts your notes on the server, where an assistant can reach them. Until you sign in, your notes stay on your device only and there is nothing for an assistant to connect to.
In the web app, create a personal API token. Give it a name, choose whether it may read only or read and write, and copy it – the token is shown once and starts with bmp_. Keep it somewhere safe, as you would a password. You can revoke a token at any time from the same screen, which cuts off anything using it immediately.
BrainMop ships an MCP server – a small program your MCP client runs for you. Configure the client to launch it with two settings:
BRAINMOP_TOKEN = the bmp_ token you just created
BRAINMOP_API_BASE = https://dabblelabs.uk/brainmop/apiOnce it is connected, the assistant gains a set of tools that match a real notes app: search and list notes, read them, create text notes and checklists, append or replace text, tick items off, reorder them, add and rename labels, and archive, trash or restore. Everything the assistant does in one session is grouped, so a whole session's changes can be undone in a single step.
Anything that can make an HTTPS request can use the same notes directly, without MCP. Send your requests to https://dabblelabs.uk/brainmop/api with the token in an Authorization header:
Authorization: Bearer bmp_your_token_hereThis is the route for another MCP-capable assistant, a custom script, or any tool that is not one of the ready-made MCP clients. The token's scope (read only, or read and write) applies the same way it does over MCP.
Whatever an assistant writes is an ordinary note: you can open it, correct it, re-file it or delete it in the app like any other. Because each batch of assistant edits is grouped, a session that went wrong is reverted in one step rather than note by note. And revoking the token ends all access straight away, over both MCP and REST.
A hosted one-click connector – where you sign in on the assistant's side and press a button to add BrainMop, with no token to copy – is still being built. Today's route is your own token plus a local MCP server or direct REST calls, as described above.
Keeping notes, syncing them across your devices, and 30 days of version history are free. Connecting an assistant and keeping full version history are part of the optional paid plan: GBP 24 a year, or GBP 4.50 a month, as an auto-renewing PayPal subscription you can cancel at any time. If the plan lapses, every note stays fully usable on the free plan – only assistant access and history beyond 30 days pause. See the Terms of Service and Privacy Policy for the full detail.