The InoatriX address
Always the same: https://mcp.inoatrix.com. This is our address, not one you host — there is nothing for your IT team to install or run.
You do not have to use the assistant built into InoatriX. If your team already works with an AI assistant, you can point it at InoatriX and configure insurance products by chatting with the assistant you already know. This page walks you through it, one step at a time.
We give you the first two. The third is whichever assistant your team already uses.
Always the same: https://mcp.inoatrix.com. This is our address, not one you host — there is nothing for your IT team to install or run.
A long private code we issue to you. Treat it like a password: it is what proves the assistant is yours.
Any assistant supporting MCP, the open standard for connecting AI to outside tools. ChatGPT and Claude are the two we show settings for below.
Do them in order. The whole thing takes about fifteen minutes.
We issue the key and send it to you — there is no sign-up form and nothing for you to create. If you have not been given one yet, ask us and we will issue it.
Treat the key like a password. Anyone who has it can configure products as you. Do not paste it into email, chat or a shared document — and tell us straight away if you think it has been seen by someone who should not have it, so we can replace it.
Ask for a separate key per assistant, or per team, if that suits you. Replacing one never disturbs the others.
This is the only fiddly step, and it is copy-and-paste. Every assistant needs the same two values — the address and your key — it is only the screen they are typed into that differs.
Open Claude's settings and find the section for connectors or MCP servers, then add a new one. Some versions give you a form: paste the address into the URL field and your key into the authorisation or token field. Others ask you to edit a settings file, in which case paste this in, replacing only the capitalised part with your key:
{
"mcpServers": {
"inoatrix": {
"type": "http",
"url": "https://mcp.inoatrix.com",
"headers": {
"Authorization": "Bearer YOUR-KEY-HERE"
}
}
}
}Open Settings → Connectors and choose to add a custom connector. Paste the address into the URL field, choose the option for an API key or token, and paste your key. Custom connectors sit under ChatGPT's developer or advanced settings and are not on every plan — if you cannot find the option, that is what to ask your IT team about.
Anything that speaks MCP will connect the same way. Look for “MCP”, “connectors” or “external tools” in its settings, give it the address above, and supply your key as a bearer token. If it asks which kind of server, choose the streaming HTTP option.
These products move their menus around between releases. The values never change: the address, the word Bearer, and your key.
Then restart the assistant completely. Not a new chat — close it and open it again. This is the single most common reason a correct setup appears not to work.
Start a new chat and ask, in these words:
List the InoatriX tools you can use.You should get back a short list of things it can do — reading what InoatriX can configure, checking a product over, building one, and looking up what it has built. If you get a list, you are connected and finished with setup. If you get an error message instead, find it in the table below.
Paste the following into the assistant's custom instructions, or simply at the top of your first message. It keeps the assistant honest and stops it inventing things InoatriX cannot do:
You can configure insurance products in InoatriX.
Always work in this order:
1. Ask InoatriX what it can configure, and read the answer.
2. Ask me questions until you have what you need.
3. Validate the product and fix every error before building it.
4. Build the product, then give me the link you get back.
Never claim a product is live. You create drafts; a person publishes them.Now just describe the product you want in plain language — the cover, the limits, who can buy it, how it is priced. The assistant will ask you about the parts you left out. When it is done it hands you a link. Open the link, review the draft in InoatriX, and publish it yourself when you are happy.
Two things surprise people the first time, and both are deliberate.
Everything your assistant creates arrives as a draft. There is no button, no phrasing and no instruction that makes it go live — the ability simply is not built into the connection. Going live stays a human decision, made by someone accountable for it, in InoatriX itself.
The configuration is complete, but products with calculated premiums still need their pricing authored before they can quote. Your assistant will tell you this rather than pretend otherwise. Products with simple fixed premiums work straight away.
Every value the assistant set is an ordinary field you can see on screen. You can open, inspect, change or undo any of it by hand. There is no AI-only setting your team cannot reach.
A key is tied to the team it was issued to. An assistant can find and change the drafts it created, and cannot see or disturb anyone else's — including work your colleagues are part-way through by hand.
Find what you were shown in the left column. The fix is on the right.
| What you see | What it means | What to do |
|---|---|---|
| The assistant says it has no InoatriX tools | It never connected. | Check the address is exactly right and starts with https://. Then fully restart the assistant — most only read their settings at startup. |
| It says your key is missing | The key was not sent at all. | The authorisation line is missing or misspelled. It must read: the word Bearer, one space, then your key. |
| It says your key is not accepted | The key was sent, but it was not recognised. | Usually a stray space or a character lost while copying. Paste it again, carefully. If that does not help, ask us for a replacement key. |
| Anything else | Most likely something on our side rather than your setup. | Get in touch and tell us what you saw. We do not need you to investigate it. |