ARTIST-MCP
READ-ONLY ARTIST WORKFLOWS
Connect OneNote to Claude Desktop or Codex. Read one musician project live, apply narrow workflow playbooks, and return one useful next result in chat.
You do not need a tidy notebook to start. Once the MCP is installed, type the highlighted lines into Claude Desktop or Codex and work through your existing pages as they are.
POINT IT AT THE MESS
List my notes and tell me what you can see.
An agent shortlists your pages by title, section, and date, then reads them. No structure required — half-written pages, loose notes, and inconsistent headings are the normal starting point.
MATCH EACH PAGE TO A PLAYBOOK
Which playbook does each of these pages call for?
It proposes the appropriate playbook for each page, based on what the page actually says rather than what its title claims — and tells you plainly when a page is too thin to call.
BUILD THE TEMPLATES YOU ACTUALLY NEED
Build the templates these pages need.
It drafts a small set of blank, reusable page templates — one for each kind of work it found, with every field left UNKNOWN so gaps stay visible instead of being invented. You paste each into OneNote once and reuse it.
CLOSE THE GAPS, ONE AT A TIME
Move my messiest page onto its template and tell me what is missing.
It puts your existing notes under the right headings, pulling in related pages, then names the empty fields and the conflicts — two different dates for the same event, a venue with no contact — and tells you which one is worth doing first.
Every template and correction is proposed in chat for you to paste — the tool reads your OneNote pages and never edits them.
Once the spring recital page is in shape, this is how it gets worked. The Orchestrator finds one useful gap — no instrument transport for 14 September — and asks before continuing. These roles hand the same page to each other, one step at a time.
ORCHESTRATOR
Offers one next action — draft the transport request? — and waits for you to say yes.
REGISTRAR
Finds the hire company already named on the recital page.
ENVOY
Drafts the transport request in chat. It never sends it.
AUDITOR
Checks that draft against the 14 September date on the page, then asks for corrections.
MUSICIAN
You read, edit, and send the final message personally.
JANITOR
Names the recital tasks that are done or expired, for you to clear.
These are temporary roles in one chat flow—not claims, queues, locks, review infrastructure, or background workers.
Install the MCP, then add the workflow Markdown to the project where you want the roles.
npx @manudota/artist-mcp init
npx @manudota/artist-mcp connect
npx @manudota/artist-mcp agents installThe playbooks above are the shipped ones, verified by checksum. To run your own instead, add --editable to init: every playbook is copied to ~/artist-mcp, yours to change, and you can add more.
Enter the key in a hidden prompt, register the MCP, then install the same workflow pack.
codex mcp add artist-notes -- npx -y @manudota/artist-mcp
npx @manudota/artist-mcp connect
npx @manudota/artist-mcp agents installOn your computer, and nowhere else. Signing in happens in your browser and the token stays on the machine you signed in on, so there is no copy of it here to lose, leak or look at. No maintainer can read your notes or mail, because nothing on our side holds the key to them.
The limit worth knowing: that token sits in a file readable by your own user account, so anything already running as you on your computer can use it. Reading your notes takes code on your specific machine — not a query someone can run from anywhere, against everyone, in silence.
HOW THIS WORKS →