Connect your business to Claude and ChatGPT
Also called: Custom MCP connector
Service 9 · Connector care plan
Keep your connector working after launch
Claude, ChatGPT and the systems you connect to keep changing, and a connector that worked last month can stop working this month. We host it, check it around the clock and update it when those services change, so most problems are fixed before your customers run into them. It's one monthly fee, and you know who to call.
- Checked every five minutes, all monthWorking
- Updated for a change in ChatGPT's connector settingsWorking
- Stock tool fixed after the shop platform changedWorking
- Security updates appliedWorking
- Questions customers asked most, for your reviewTo do
A made-up month. You get a short note like this every month.
Why connectors need looking after
The assistants change often
Claude and ChatGPT update how connectors are added, signed in to and shown. Most changes are small; a few break things.
So do your other systems
Shop platforms, booking tools and payment providers change their APIs too. A tool that read stock yesterday can return nothing today.
Customers don't tell you
When a connector fails, people usually just give up. Checking it constantly is the only way to know before they do.
What the connector care plan includes
One monthly fee, agreed up front. No surprise invoices for keeping things working.
Hosting
On a secure server in Europe, with backups and a secure connection, kept up to date.
Checks around the clock
Automatic checks every few minutes that the connector answers and its tools return sensible results. A person is alerted when they don't.
Updates when things change
When Claude, ChatGPT or a connected service changes, we update the connector and test it again.
Security updates
Software updates applied promptly, and a short safety check each quarter.
A monthly note
What we checked, what we changed, and anything worth your attention, in a few lines.
Someone to call
A named person who knows your connector, by email, with a reply within one working day.
How connector care works
Step 1: We look it over
If we didn't build your connector, we review it first so we know what we're taking on.
Step 2: We move it in
Onto our hosting, or we watch it where it already runs, whichever suits.
Step 3: We watch and update
Checks every few minutes, updates when things change, a note each month.
Step 4: You can leave any time
With notice, and with everything handed back: code, settings and documentation.
Is it right for you?
A good fit if
- You have a connector that customers or your team rely on.
- You don't have a developer on hand to keep an eye on it.
- You'd rather pay a known monthly fee than fix things in a rush.
Probably not for you if
- You have your own developers who already monitor and maintain it.
What we need from you
Access to the connector's code and hosting (or permission to move it), and the accounts it connects to.
Questions about connector care
Do you only look after connectors you built?
No. We'll review a connector someone else built and take it on if it's sound, or tell you what needs fixing first.
What counts as a change rather than care?
Keeping it working is care. Adding a new tool or a new kind of question is new work, which we quote separately.
Where is it hosted?
On servers in the EU, with nightly backups. If you'd rather host it yourself, we can monitor it where it is.
How much does it cost?
A fixed monthly fee, depending on how many connectors and tools you have. Quoted after a short chat.
Talk to us about a care plan
Tell us about your connector, who built it and where it runs now.
A real person reads every note. There's no obligation, and we'll tell you honestly if we're not the right people for it.
Often goes with
Make sure your connector is safe before customers use it
Also called: MCP security review
Put AI to work while others are still watching
Also called: Agent integration