The Warrior Network is a group of separate music sites with one rule: every subject has exactly one home. A guitar question belongs to the guitar site, a scale’s formula to the theory site, a pedal steel’s copedent to the steel site. That rule serves a reader who can pick the right site. An AI client asking on a reader’s behalf cannot — and without help, it answers from whatever it half-remembers.
An endpoint, not a chatbot
The Model Context Protocol lets an AI client call a tool and read back a structured answer. Music Warrior AI is being built as one such endpoint for the whole network: a client adds one address, asks a music question, and gets back an answer read from a page a sister site already publishes — never text written here for the occasion and passed off as a source.
Every answer cites its page
The endpoint’s one promise is the citation. The notes of a chord arrive with the chord page that spells them, on the site that owns that instrument; a scale arrives with its scale page. A reader who wants the whole picture — the diagram, the neighbouring shapes, the sound — follows the link. Where an answer would have no page behind it, the endpoint is meant to say so rather than answer.
Kept apart from the portal
The network already has a front door for people: Music Warrior Network, the portal, which says in prose which site answers which question. This site is the door for software. It publishes no directory and no page per site, so a question about which site to open belongs to the portal, whose card is on this site’s network page.
What is here today
The endpoint answers at https://musicwarrior.ai/mcp, built on the same shared factory the network’s hub serves its own MCP endpoint from. The home page is its install page — the endpoint’s address, how to add it to a client, and the tools it offers — and privacy says exactly what the endpoint does with a request.