for developers
Connect your agent in one command or one click.
Once connected, Claude Code, Cursor, claude.ai or Claude Desktop reads and writes the blocks on your maps. The server sends your agent no instructions of its own, so it writes to your maps only when you ask.
One click, and no key to paste
In claude.ai or Claude Desktop, add the server address from the config as a connector. Corlecti Map opens, you approve the connection while signed in, and you are back in your client. Settings → MCP Server lists every connection you approved, and removing one cuts that client off from your maps at once.
A key for Claude Code or Cursor
Create one per repository in Settings → MCP Server, and name it after that repository. It starts with mmap_live_ and is shown once, so copy it straight away. Run the command inside that repository, and Claude Code keeps the key for that project alone.
In a terminal, inside the repository, for Claude Code
claude mcp add --transport http corlecti-map https://map.corlecti.com/api/mcp \
--header "Authorization: Bearer mmap_live_YOUR_KEY"In the config file of Cursor or another client
{
"mcpServers": {
"corlecti-map": {
"type": "http",
"url": "https://map.corlecti.com/api/mcp",
"headers": { "Authorization": "Bearer mmap_live_YOUR_KEY" }
}
}
}keys
Each repository gets a key to its own map.
When you create a key, you choose what it may reach: every map, one map, or one folder. The choice stays with the key; for a different reach, create a new key and revoke the old one.
One map
Your agent sees every other map as “not found”. Tools that act on your whole account are not offered to it. Its searches cover that map alone.
One folder
It reaches every map inside the folder, and a map it creates lands in that folder too. Keep a project's maps in one folder, and one key covers them all.
A model and effort of its own
A key that reaches every map can carry its own model and reasoning effort. They apply only when your agent calls delegate to hand a task to the agent in the map's chat. Those tasks use your AI allowance.
Keys per plan
The free plan holds 5 live keys, Pro 25 and Workspace 50. A key you revoke stops counting.
telegram
Talk to your map from your own Telegram bot.
Create a bot with Telegram's BotFather and connect it in Settings → Telegram. It answers you, and nobody else until you add guests. The free plan includes 1 bot of your own, Pro 5, and Workspace as many as you need.
It answers as the map's chat
Write to it, and the agent in the map's chat replies in Telegram. It is the same conversation as in the browser: what you typed on the train is there at your desk.
Or it keeps notes
Switch it to capturing, and every message becomes a block on its map. The bot writes out a voice note first, then handles it as if you had typed it.
Your key, or the shared one
On Corlecti Map's shared key, the bot's turns use your AI allowance.
One map, or all of them
Point a bot at one map, and it writes there and searches nothing else. Leave it open to every map, and /map picks where the next message goes.
The bot does not take photos, files or stickers. It says so, and saves nothing.
guests
A colleague's note lands on your map.
On Pro and Workspace, up to 5 people besides you can write to each bot of yours. Their messages become blocks on the bot's map, and they cannot read the map through the bot. Each message they send uses your AI allowance.
By username
Add a person by their Telegram username in the bot's settings. From their next message on, what they send lands on the map as a block. Remove them there, and they can no longer write to the bot; what they already sent stays on your map.
Guest access without names
Some people have no username, or you do not know it. Choose how many may come in and for how long. Whoever writes to the bot in that time becomes a guest, up to the number you chose.
A contact form that files leads into a map.
Your site's backend holds an MCP key narrowed to one map. On every submission it calls the MCP tool apply_map, and the person arrives as a block: name, company, question.
If that key leaks, it opens one map of yours, and you revoke it in Settings → MCP Server. Before writing, your backend can search the map and update the block of someone who writes again.
If any part of a write is invalid, nothing is written. An Idempotency-Key header makes a retry safe after a dropped connection. Any script can do this: it sends the key in an Authorization header to the server address from the config.
In the morning, each of yesterday's leads is a block on that map.
More situations like this one, as real maps: Use cases
Create a key and connect your agent.
Guests need Pro or Workspace. The keys, the connector and a bot of your own come with the free plan.