Skip to content

MCP server: let Claude, ChatGPT or Cursor use your dataSoon

The assistant's tools — tasks, notes, tables, automations — offered to any MCP client with a token you control. In the works.

The assistant inside the app is one client of your data. It does not have to be the only one. The backend already speaks MCP to its own assistant; opening that server to the AI tools you already use, with a token per client, is what we are building next.

What will be exposed

The tool set the built-in assistant uses — create_task, update_note, list_tables, describe_table, query, create_automation and the rest — scoped to your account. Results carry the same wiki links, so a note created from Cursor links to the task created from Claude.

Connecting

Create a token in the app, paste the server URL and the token into your client’s MCP configuration, and the tools appear. The guide describes the planned flow for Claude Desktop.

Why this matters

Your data stops being trapped in one assistant’s context. Draft in Claude, file in the assistant, report in your browser — all against one set of records that you own.

Questions

What is MCP?

The Model Context Protocol, an open standard for giving AI assistants tools and data. Claude, ChatGPT, Cursor and many others speak it.

What will a connected client be able to do?

What the tools allow: list and search notes and tasks, create and update them, describe and query tables, create automations. The same tools our own assistant uses.

Will I be able to revoke access?

Yes. Access will be a token you create and can delete at any time.

Related

Start with one message

Open the bot, say what's on your mind, and see it become a task.

Join in TelegramJoin with email

Closed beta: we let people in in batches. Sign up in Telegram or with your email, and we'll let you know when your access opens.