Documentation

Corlecti Map is a map of what you know: blocks on an infinite canvas, the links between them, and several ways of looking at the same material. Most of it needs no documentation — you open a map and write.

These five pages are for the parts that talk to something else, or that answer "how much" and "what if" precisely rather than in passing.

MCP server

For anyone who wants their AI assistant to read and write their maps. If you use Claude Code, Claude Desktop, Cursor, claude.ai or anything else that speaks the Model Context Protocol, this is how you connect it, and what it can then do.

Start here. It is the shortest of the five and it is what most people came for.

API

For anyone writing a script or a service. What the supported programmatic surface is, how a request authenticates, and what an error means when you get one.

The .mmap format

For anyone generating a map rather than drawing one. The document format that describes blocks and links, and what happens when one is imported. You need this if you are producing maps from something else; you do not need it to use the app, and you do not need it to connect an assistant.

Limits

For anyone who wants the exact numbers. The AI allowance and its two windows, the MCP call quota, rate limits, every refusal code, what each plan includes, and what your own provider key changes.

Recipes

For anyone about to build something. Your own Telegram bot under your own name, letting somebody else write into it, a key seated on one branch (coming), and a system of your own filing material into a map through MCP.

Something missing, wrong, or out of date? Write to [email protected].