Notes

What you wrote down, and what an agent wrote down for you

Calling it

This is your own data, so a call has to say who you are. Make a token at /token and send it as a header.

curl -H "Authorization: Bearer $MU_TOKEN" \
  https://mu-mcp.yvangodard.me/api/v1/notes/list

How every call behaves →

Methods

POST /api/v1/notes/add

Write a note under a title, so it is there next conversation. Writing a title that exists rewrites that note

Needs an account. Changes something, so POST only.

Argument	Type	Description
`title` *	string	What the note is called, e.g. "location" or "project brief". Writing a title that exists rewrites that note
`text` *	string	What the note says

curl -X POST \
  -H "Authorization: Bearer $MU_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"text","title":"title"}' \
  https://mu-mcp.yvangodard.me/api/v1/notes/add

title *text *

POST /api/v1/notes/delete

Delete one note by title

Needs an account. Changes something, so POST only. Withheld from the agent — a person or a program only.

Argument	Type	Description
`title` *	string	The note to delete, as returned by notes_list

curl -X POST \
  -H "Authorization: Bearer $MU_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"title":"title"}' \
  https://mu-mcp.yvangodard.me/api/v1/notes/delete

title *

GET /api/v1/notes/get

Read one note by title. Use it when you know the title; notes_list when you do not

Needs an account.

Argument	Type	Description
`title` *	string	The note's title, as given to notes_add

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://mu-mcp.yvangodard.me/api/v1/notes/get?title=title"

title *

GET /api/v1/notes/list

List every note the caller has written, with its text

Needs an account.

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://mu-mcp.yvangodard.me/api/v1/notes/list"

The same methods are tools over MCP, and every service on this instance is in one reference. Same method, same answer, same price.