# Milanote API and MCP server

> Milanote has no public API and no official MCP server (checked 11 Oct 2026). A Public API and an MCP server are open feature requests on its public roadmap, and the only way to get content out is to export a board by hand.

Visual workspace for creative work: boards of notes, images, links, files and to-do lists, laid out like a moodboard, with boards nested inside boards.

## What is the Milanote API?

Cotlet's Milanote API exposes 11 endpoints for your own Milanote account: list boards, get board, search boards, export board, create board, add note, add link, upload image, add to-do list, add comment and invite editor. The list_boards endpoint returns your boards and nested sub-boards, with title, parent board and ID. Each endpoint takes simple JSON inputs like board_id, parent_board_id or title and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 11 (4 read, 7 write)
- **Updated:** 2026-10-11

Milanote has no public API and no official MCP server (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Milanote with 11 endpoints (4 read, 7 write): your AI agent signs in as you and does the work.

## Does Milanote have an official API?

Milanote has no public API and no official MCP server (checked 11 Oct 2026). A Public API and an MCP server are open feature requests on its public roadmap, and the only way to get content out is to export a board by hand.

| Task | Milanote official | Cotlet |
|---|---|---|
| List boards and read their cards | No | Yes |
| Search across all boards | No | Yes |
| Add notes and links to a board | No | Yes |
| Upload images to a board | No | Yes |
| Add to-do lists with due dates | No | Yes |
| Export a board as Markdown, PDF or Word | Partly: Export button in the app only, no API | Yes |
| Comment on a board | No | Yes |
| Invite editors to a board | No | Yes |

Sources: [Milanote Help: Exporting your work](https://help.milanote.com/en/articles/111395-exporting-your-work), [Milanote roadmap: Public API](https://poll.milanote.com/c/48-public-api), [Milanote Help: Sharing a board](https://help.milanote.com/en/articles/4324593-sharing-a-board), [Milanote terms of service](https://www.milanote.com/legal/terms-of-service), [Milanote Help: To-Do Lists](https://help.milanote.com/en/articles/10486983-to-do-lists)

## For AI agents

```text
Milanote has no public API and no official MCP server (checked 11 Oct 2026). A Public API and an MCP server are open feature requests on its public roadmap, and the only way to get content out is to export a board by hand.
Cotlet provides a hosted MCP server and REST API for Milanote: 11 tools (4 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=milanote; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/milanote
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_boards, get_board, search_boards, export_board, create_board, add_note, add_link, upload_image, add_todo_list, add_comment, invite_editor
Confirm      add_comment, invite_editor (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/milanote-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=milanote (Milanote is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Milanote once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Milanote server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Milanote MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Milanote in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Milanote's terms; Cotlet is not affiliated with Milanote.
```

## What can an AI agent do in Milanote?

Cotlet is best for creatives, writers and small teams who keep their plans and references in Milanote and want an agent to fill and read boards without running or fixing a server.

- **[Save links and images to a Milanote moodboard](https://cotlet.dev/integrations/milanote-api-mcp-server/save-links-to-moodboard)**: "Here are the references from this week: 12 links from our Slack thread and the screenshots in ./refs. Put them on the Moodboard sub-board of Brand refresh, skip anything already there, and tell me what did not fit." → `list_boards`, `get_board`, `add_link`, `upload_image`
- **[Export a Milanote board to Markdown](https://cotlet.dev/integrations/milanote-api-mcp-server/export-board-to-markdown)**: "Export my Novel outline board and each of its chapter sub-boards as Markdown into ./outline, one file per board." → `list_boards`, `get_board`, `export_board`
- **[Turn call notes into a Milanote to-do list with due dates](https://cotlet.dev/integrations/milanote-api-mcp-server/add-todo-list-with-due-dates)**: "Here is the transcript of today's client call. Add the action items as a to-do list on my Q1 campaign board, with the dates we agreed, and leave out anything that is already on the board." → `list_boards`, `get_board`, `add_todo_list`
- **Upload images to a Milanote board**: "Upload every image in ./shots to a new board called Location scout." → `create_board`, `upload_image`
- **Search all your Milanote boards**: "Where did I save that note about the color palette?" → `search_boards`, `get_board`

## Can Milanote automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Milanote connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/milanote/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/milanote/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/milanote/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/milanote/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Milanote.

### list_boards

Your boards and nested sub-boards, with title, parent board and ID. Access: read. REST: `POST /api/v1/milanote/list_boards`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `parent_board_id` | string | no | Only boards inside this board. Default: your boards at the top level. |
| `limit` | integer | no | Number of boards to return. Default: 50. |

Returns boards in the order they appear in Milanote, each with its parent so nesting is clear. Boards can sit inside boards, like folders, so use parent_board_id to walk down. Your Home board is not a regular board and is not listed.

Example response:

```json
{
  "boards": [
    {
      "id": "b_7Kq2Lm",
      "title": "Brand refresh",
      "parent_board_id": null
    },
    {
      "id": "b_2Xn9Dc",
      "title": "Novel outline",
      "parent_board_id": null
    },
    {
      "id": "b_5Hc3Wp",
      "title": "Q1 campaign",
      "parent_board_id": null
    }
  ]
}
```

### get_board

Every card on a board: notes, links, images, files, to-do lists and sub-boards. Access: read. REST: `POST /api/v1/milanote/get_board`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `include_comments` | boolean | no | Also return comment cards and their replies. Default: false. |

Returns one entry per card with its type, text or URL, and ID, so other tools can point at it. To-do list cards include each task with its done state and due date. Sub-boards appear as cards with their own board_id; call get_board again to open one. Reads only, so it works on boards you can view as well as edit.

Example response:

```json
{
  "board_id": "b_5Hc3Wp",
  "title": "Q1 campaign",
  "cards": [
    {
      "id": "c_41aF",
      "type": "note",
      "text": "Palette: warm greys with one orange accent."
    },
    {
      "id": "c_88bQ",
      "type": "link",
      "url": "https://example.com/type-specimen",
      "title": "Type specimen"
    },
    {
      "id": "c_12dK",
      "type": "board",
      "board_id": "b_5Hc3Xt",
      "title": "Social assets"
    }
  ]
}
```

### search_boards

Find notes and boards by text across all your boards, like the in-app search. Access: read. REST: `POST /api/v1/milanote/search_boards`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Text to look for. |
| `sort` | enum | no | last_viewed or last_modified. Default: last_viewed. |

Searches the board you have open and the contents of every other board you have created, as the Search icon in Milanote does. Results are sorted by last viewed unless you ask for last modified. Use get_board on a hit to read its cards.

Example response:

```json
{
  "results": [
    {
      "board_id": "b_5Hc3Wp",
      "board_title": "Q1 campaign",
      "card_id": "c_41aF",
      "snippet": "Palette: warm greys with one orange accent."
    },
    {
      "board_id": "b_7Kq2Lm",
      "board_title": "Brand refresh",
      "card_id": "c_30pM",
      "snippet": "Color palette v2 from the workshop"
    }
  ]
}
```

### export_board

Export a board in one of the formats Milanote offers. Access: read. REST: `POST /api/v1/milanote/export_board`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `format` | enum | yes | markdown, plain_text, word, pdf or png. |

Runs the same export as the Export button on a board and returns the text, or a download link for word, pdf and png. Home boards cannot be exported. PDF and PNG are limited to a single page; Word spreads a large board over several pages.

Example response:

```json
{
  "board_id": "b_2Xn9Dc",
  "format": "markdown",
  "content": "# Novel outline\n\n## Act one\n\n- Maya finds the letter\n- The ferry leaves without her\n"
}
```

### create_board

New board, at the top level or nested inside another board. Access: write. REST: `POST /api/v1/milanote/create_board`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `title` | string | yes | Board title. |
| `parent_board_id` | string | no | Board to nest it in. Default: top level. |

Returns the new board ID for the tools that add cards. The board is private to you until you share it. It reaches no one, so it runs without asking; move it to the trash in Milanote to undo it.

Example response:

```json
{
  "board_id": "b_9Rt4Zy",
  "title": "Location scout",
  "parent_board_id": null,
  "board_url": "https://app.milanote.com/b_9Rt4Zy"
}
```

### add_note

Note card with text, placed on a board. Access: write. REST: `POST /api/v1/milanote/add_note`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `text` | string | yes | Note text. |

Adds one note card and returns its ID. On the free plan a note counts toward the 100 notes, images or links total. Other editors of the board see the card, but nobody is notified, so it runs without asking; drag it to the trash to undo it.

Example response:

```json
{
  "card_id": "c_62tN",
  "board_id": "b_5Hc3Wp",
  "type": "note",
  "text": "Kickoff moved to Tuesday."
}
```

### add_link

Link card for a web address, placed on a board. Access: write. REST: `POST /api/v1/milanote/add_link`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `url` | string | yes | Web address to save. |

Adds one link card and returns its ID and title. On the free plan a link counts toward the 100 notes, images or links total. Nobody is notified, so it runs without asking; drag the card to the trash to undo it.

Example response:

```json
{
  "card_id": "c_77sW",
  "board_id": "b_7Kq2Lm",
  "type": "link",
  "title": "Type specimen",
  "url": "https://example.com/type-specimen",
  "board_url": "https://app.milanote.com/b_7Kq2Lm"
}
```

### upload_image

Image card from a file, placed on a board. Access: write. REST: `POST /api/v1/milanote/upload_image`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `file_base64` | string | yes | Image file contents, base64. |
| `file_name` | string | no | File name shown on the card, e.g. location-01.jpg. |

Adds one image card per call and returns its ID. On the free plan an image counts toward the 100 notes, images or links total, and file uploads are capped at 10. Nobody is notified, so it runs without asking; drag the card to the trash to undo it.

Example response:

```json
{
  "card_id": "c_90uE",
  "board_id": "b_9Rt4Zy",
  "type": "image",
  "file_name": "location-01.jpg"
}
```

### add_todo_list

To-do list card with tasks, each with an optional due date. Access: write. REST: `POST /api/v1/milanote/add_todo_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `title` | string | no | List title. |
| `tasks` | object | yes | Array of { text, due_date?, due_time? }; due_date is YYYY-MM-DD, due_time HH:MM for the reminder. |

Creates one to-do list with all its tasks and returns each task ID. A due date makes Milanote remind whoever set it, by email, phone push or browser notification, as their settings say. Nobody is notified when the list is created, so it runs without asking; drag it to the trash to undo it.

Example response:

```json
{
  "card_id": "c_55vG",
  "board_id": "b_5Hc3Wp",
  "title": "Call edits",
  "task_count": 2,
  "tasks": [
    {
      "id": "t_01",
      "text": "Shorten the intro",
      "due_date": "2026-10-16"
    },
    {
      "id": "t_02",
      "text": "Swap the hero image",
      "due_date": "2026-10-16"
    }
  ]
}
```

### add_comment

Comment card on a board, or a reply in a comment thread, as you. Access: write, asks the user first. REST: `POST /api/v1/milanote/add_comment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `text` | string | yes | Comment text. @name tags a collaborator. |
| `reply_to_id` | string | no | Comment ID to reply to. |

Posts under your name; people in the thread and anyone you @mention are notified. A comment cannot be deleted from a thread afterwards, and only you can edit it. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "comment_id": "m_31jB",
  "board_id": "b_5Hc3Wp",
  "text": "@Sam the new palette is on this board.",
  "notified": [
    "Sam"
  ]
}
```

### invite_editor

Invite someone by email to edit a board and its sub-boards. Access: write, asks the user first. REST: `POST /api/v1/milanote/invite_editor`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `board_id` | string | yes | Board ID from list_boards or the board URL. |
| `email` | string | yes | Their email address. |

Sends the invitee an email with a link; they need a free Milanote account to edit. Sharing also applies to sub-boards, and your Home board cannot be shared. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "board_id": "b_7Kq2Lm",
  "invited": "sam@example.com",
  "role": "editor",
  "status": "invited"
}
```

## How do I connect Milanote to Claude Code, Codex or Cursor?

Connecting Milanote takes three steps: request access, sign in to Milanote once, then add one MCP server or call the REST API with the same key.

### Connect Milanote to your agent.

1. **Create an account** Sign up and add Milanote in the console. Your API key is there too.

2. **Sign in to Milanote once** Open the connect page from the console and sign in to Milanote the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Milanote tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Here are the references from this week: 12 links from our Slack thread and the screenshots in ./refs. Put them on the Moodboard sub-board of Brand refresh, skip anything already there, and tell me what did not fit.
```

### Call Milanote from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/milanote/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/milanote/add_link \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"board_id":"b_7Kq2Lm","url":"https://example.com/type-specimen"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "card_id": "c_77sW",
  "board_id": "b_7Kq2Lm",
  "type": "link",
  "title": "Type specimen",
  "url": "https://example.com/type-specimen",
  "board_url": "https://app.milanote.com/b_7Kq2Lm"
}
```

## Why use Cotlet for Milanote?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Milanote yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Milanote changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Milanote MCP server on GitHub?

Yes. Community Milanote MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, sign it in to Milanote, and keep it running yourself; when Milanote changes its site, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Download or clone it, sign it in to Milanote, add it to each MCP client | Request access, sign in to Milanote once, add one MCP server or API key |
| When Milanote changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Milanote session | On your computer, stored however that tool stores it | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| When the session expires | Tools fail until you sign in again by hand | We keep it alive; if Milanote logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Milanote changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Milanote API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Milanote API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Milanote account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Milanote yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Milanote tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Milanote in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Milanote's terms:** You use your own Milanote account and stay responsible for following Milanote's terms. Cotlet is independent and not affiliated with Milanote. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Milanote. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Milanote once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Milanote session would leave my computer.**

Cotlet keeps your Milanote session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Does it work on Milanote's free plan?**

Yes, for anything your account can do in the app. The free plan allows 100 notes, images or links and 10 file uploads in total (Milanote plans page, checked 11 Oct 2026), and the same caps apply to calls.

**Can it export my Home board?**

No. Milanote does not allow exporting a Home board, so export_board works on the boards inside it.

**Can my agent post or send messages in Milanote without asking me?**

No. Every call to add_comment or invite_editor waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_board, add_note, add_link, upload_image, add_todo_list runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Milanote API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/milanote/{tool} from the HTTP Request node.