Your MCP Host
An address that carries your name, and a page that installs it.
Every MCP setup gets its own host. Below we show what a reader finds when they open it: a page that installs the connection in their assistant, a skill that teaches that assistant to use your content well, and the endpoint itself.
Try one
Miso runs a public host you can connect to right now. It carries the Wikinews archive, and it is built the same way as yours:
https://wikinews.mcp.miso.ai
Open it in a browser to see the install page. In Claude Code, two commands give you the connection and the skill:
/plugin marketplace add https://wikinews.mcp.miso.ai/marketplace.json
/plugin install wikinews-mcp-plugin@wikinews
Sign in with an email address on first use. Access lasts 30 days. Then ask your assistant something the archive covers, such as what happened at the 2012 Olympics opening ceremony, and watch it search, read the full article, and cite it.
Every path in the next section answers on that host, so you can also open
/llms.txt or /marketplace.json and read what a client reads.
A Miso product demo, with content from Wikinews under CC BY 2.5. It is not affiliated with Wikinews or the Wikimedia Foundation. The archive runs through 2013.
The address
The host can be a Miso subdomain, or a name on your own domain.
| Shape | Example | What you do |
|---|---|---|
| Miso subdomain | your-site.mcp.miso.ai |
Nothing. Miso runs the DNS. |
| Your own domain | mcp.your-site.com |
Point a CNAME at Miso. |
Your own domain is the one to pick when subscribers will see the address. It keeps your brand on the connection, in the assistant's settings screen, and in the sign-in prompt. Any shape of name works: a subdomain, a deep subdomain, or your apex domain.
Miso maps the host to your content when the host is set up. A name that was
never declared returns 404, so no other address can serve your content.
The endpoint your subscribers connect to is /mcp on that host:
https://mcp.your-site.com/mcp
What a Miso MCP server host serves
Miso runs the host. These answer on it from the day it is set up.
Each path below links to the live demo host, so you can open it and read what a client reads.
| Path | What it is |
|---|---|
/ |
The install page. A reader picks their assistant and copies one command. |
/mcp |
The MCP endpoint. Your subscribers sign in here. |
/marketplace.json |
The plugin catalog, for a one-command install in Claude Code. |
/plugin.zip |
The plugin itself: the connection and the skill together. |
/skills.zip |
The skill on its own, for every other assistant. |
/llms.txt |
A plain-text index of all of the above, for an agent that lands on the host. |
/.well-known/… |
The sign-in metadata a client reads before it connects. |
Two of those links download a file, and /mcp answers 405 in a browser. The
endpoint speaks JSON-RPC over POST, and answering a browser GET that way is
what the transport specification asks for.
You build none of these. The content carries your brand name and your tool names.
The install page
https://mcp.your-site.com/ is a page you can send to a subscriber, or link
from your account settings. It shows your name, what the connection gives
them, and a tab for each assistant: Claude Code, Cursor, Codex, Gemini CLI,
Claude Desktop and ChatGPT. Each tab holds the exact command for that client.
The page has two halves. The first installs the plugin, which is the connection and the skill in one step. The second connects the endpoint on its own, for a reader who wants the tools and no more.
The plugin, and what is in it
In Claude Code, two commands install everything:
/plugin marketplace add https://mcp.your-site.com/marketplace.json
/plugin install your-site-mcp-plugin@your-site
That install carries two pieces:
The connection. The MCP endpoint, already pointed at your host, so the reader types no URL and pastes no key. They sign in on first use.
A skill. A short set of instructions that loads into the assistant alongside your tools. It teaches the assistant how to get good answers from your archive: search before answering, rephrase and try again when the first search misses, open the full article when detail matters, and cite the title and URL of everything it used. It also states what your archive does not cover, so the assistant says so rather than inventing an answer.
The skill is the part that changes answer quality. A connection alone gives an assistant your tools. The skill tells it how you want them used.
Every other assistant
The one-command install is specific to Claude Code. Every other assistant loads the same skill from a folder, so the host serves it as a plain archive:
curl -sL https://mcp.your-site.com/skills.zip -o /tmp/skill.zip
unzip -o /tmp/skill.zip -d ~/.cursor/skills/
The archive holds the skill folders at its top level, so it unzips straight
into the assistant's skills directory. Change the last path for the client in
front of you: ~/.cursor/skills/ for Cursor, ~/.agents/skills/ for Codex,
~/.gemini/skills/ for Gemini CLI. In ChatGPT, download the file and upload
it under Plugins.
The endpoint is added separately in those clients, with one command:
codex mcp add your-site --url https://mcp.your-site.com/mcp
The install page carries the version of this for each client, so a subscriber copies rather than adapts.
The index for agents
https://mcp.your-site.com/llms.txt describes the host in plain text: what
the archive covers, where the install page is, the endpoint URL, the plugin
commands, and the name and purpose of each tool. An agent that is handed your
host and no instructions reads this file and knows what to do with it.
Getting a host
Miso sets up the host with you. Two things are agreed:
- The name. A Miso subdomain needs nothing from you. Your own domain needs a CNAME record, which Miso gives you.
- The wording. Your brand name, what the archive covers, the tool names, and anything you want the assistant told about your content.
Sign-in for subscribers is set up at the same time. See MCP — for your Subscribers for what your login page does.
Next
- MCP — for your Subscribers — the sign-in hand-off.
- MCP — Internal Use — one credential for your own team.
- Tools API — run your own MCP server on Miso's tools.
