In short
- One address per agent.Each agent gets its own hosted MCP server, ready to share.
- A key that reaches one agent.The key is bound to that agent and cannot read anything else in your workspace.
- Cited answers, like your chat.Users get the same sourced answers your website chat gives.
- Two simple tools.search_docs finds passages, ask_agent returns a full cited answer.
If you sell to developers, your docs now compete with their AI assistant. When the assistant guesses, your users get outdated or wrong code. A hosted MCP server fixes that: their assistant asks your agent directly and answers from your real documentation, with links to the pages it used.
How it works
MCP, the Model Context Protocol, is the open standard AI assistants use to connect to outside services. Every OneType agent can have its own hosted MCP server at an address that ends in the agent's id. You create a key for that one agent, share the address and the key with your users, and they add it to Cursor, Claude Code or any MCP client.
- Open Developer, MCP, and find the agent's card.
- Create the agent's key. It is shown once.
- Copy the ready-made snippet with the key filled in.
- Share it in your docs or onboarding, and users paste it into their client.
What your users get
Two tools. search_docs returns the passages of your agent's pages, files and Q&A that best match a question, each with a score and its source. ask_agent returns a full answer from your agent with citations, just like the chat on your site. Then a user can type, in their editor, how do I verify a webhook signature, and get your answer, not a guess.
Each ask_agent call counts like a chat reply on your website: in AI credits. Premium with your own AI key, which will count answers instead, is coming soon.
Safe to share
The key holds a single permission and is bound to one agent. It cannot list conversations, read contacts or reach another agent, and the agent is fixed by the address, not by anything the client sends. Passages and answers are marked as untrusted text for the calling model, so text in your docs cannot instruct the user's assistant. Every call is recorded in your audit log, and revoking the key stops it on the next request.
Plans
Hosted MCP per agent is on every paid plan: Premium and Enterprise. Not on Free.
Why it beats a docs link
A link sends a developer away from their work. An MCP server brings the answer into the editor where they are already asking questions. Because the answers come from the same agent as your website chat, they follow the same knowledge, and when you update your docs the agent learns from the new pages on its usual schedule. There is nothing extra to maintain for the MCP server itself.
You stay in control of who can use it. Create the key when you are ready to share, put it in your developer docs or onboarding email, and revoke it whenever you want to stop access. You can create a new key from the same card.