Audiotool 3.0 made the DAW multiplayer, and NEXUS opened it to everyone — including AI, straight into the session over MCP. That was the bold half. The other half is that a language model still can't reason reliably about harmony. THIRI is the theory layer that makes your promise concrete.
Step through the integration. The tool calls are real and the outputs are the engine's documented answers — this is the exact loop NEXUS + thiri-mcp makes possible, and the build we're bringing to the Audiotool challenge.
Each starts from a call you've already made — the platform, the partners, the audience — and pairs it with a piece that exists now. The first steps are small on purpose.
NEXUS gives third parties reach into "virtually every part of Audiotool" — free, no license fees, with Splice and Ujam already inside. An open platform earns its bet through the partners who show up early with something real.
A THIRI chord device for the session. A harmony panel any collaborator can use — progressions, voicings, reharmonization — writing chord-skeleton MIDI into the project through @audiotool/nexus, in real time, for everyone in the room.
FIRST STEP — a session with the device in it. We'll send the invite link.
The NEXUS showcase leads with a community-built Harmony Editor — clear demand for chord tools, proven by your own builders. Demand like that deserves an engine underneath it.
The production-grade version of that idea. Deterministic analysis, instrument-ready voicings, voice-leading scores, eight reharmonization techniques — an API the whole ecosystem's chord tools can stand on, so community builders get depth for free.
FIRST STEP — we back one community harmony tool with the engine and compare.
Letting creators bring their own LLM into a live session is the boldest AI move any DAW has made. The demo that sells it is the one where the agent's musical suggestions are actually correct.
thiri-mcp — chord-correct reasoning for every agent that enters. Hosted, live today, already on npm and in Claude and Cursor workflows. Wire an agent to thiri-mcp and a NEXUS session and you have the flagship demo of your own platform story.
FIRST STEP — point any agent at mcp.thiri.ai; the flow above runs today through step 2.
"Google Docs meets a creative sandbox" — plus the esports partnerships — says it plainly: your next million users arrive expecting play, not prerequisites. Theory is the wall they hit first.
Harmony as guidance, not homework. In-session rails — suggest the next chord, stay-in-key hints, one-tap reharmonize — powered by the same engine behind Run The Changes, our shipped practice game that turns chord charts into levels. We've gamified theory before; it works.
FIRST STEP — one guided-harmony interaction, prototyped in the chord device.
The Let's Build! series and the Music Technology Hackathon Montreal are exactly how a platform finds its builders — and how builders find the team. We took the invitation.
An Audiotool-challenge entry, in person. Our two-person team is registered for Montreal (Aug 22–23): the THIRI chord device as the core, built on NEXUS and demoed live — and, if the weekend smiles, a finale where a whole band arrives from a chat prompt and lands as tracks in the session. You'll meet the work before you meet the deck.
FIRST STEP — see you at the Wednesday prep calls.
The SDK is young and moving fast — which is precisely when serious integrations shape the platform. The device APIs that music-intelligence tools need get designed now, with the partners who build now.
A committed early integration — and the feedback that comes with it. We build against moving APIs for a living (the MCP ecosystem moves monthly). Our chord device doubles as a real-world stress test of NEXUS document editing, sync, and MCP surfaces — findings shared as we go.
FIRST STEP — a shared channel with your platform team.
THIRI computes chords, voicings, voice-leading, and reharmonization from pitch-class-set theory — the same answer every time, in milliseconds, from a production API. It ships in the exact shapes NEXUS speaks: an MCP server for agents, a REST API for devices, and an n8n node for workflows.
thiri-mcp is live, the chord device is our Montreal build, and your platform story gets its flagship proof either way. If the harmony layer belongs in the launch-partner tier, let's make it official — the first step is smaller than a meeting.
dennison@bluesprincemedia.com · engine live at chords.thiri.ai · MCP at mcp.thiri.ai · see you in Montreal, Aug 22–23