Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Managed MCP server hosting

An MCP server is not a thing you ship once. The spec keeps moving, provider APIs drift, and OAuth tokens expire. We host, monitor, and maintain every connector we build, from $500 per month, so it keeps working while your team just uses Claude.

Build my connectorBook a scoping call

Hosting

The server runs on our infrastructure. Your team never deploys, patches, or restarts anything.

Monitoring

We watch the connector so a failure is our problem to notice, not something your team discovers mid-conversation.

Token health

OAuth tokens expire and grants get revoked. We manage the credential lifecycle so access does not quietly rot.

API-change fixes

When a vendor renames a field, deprecates an endpoint, or changes auth, we fix the connector on our clock.

MCP spec migrations

The MCP specification has shipped multiple revisions in the last year. We migrate the server so it keeps pace with what Claude expects.

Extensions over time

When your tool adds fields or endpoints you want Claude to use, the connector grows with it.

Key takeaways

  • Managed hosting covers the server itself plus monitoring, OAuth token health, fixes when provider APIs change, and migrations as the MCP spec evolves.
  • MCP is a young, fast-moving protocol: the spec has shipped multiple revisions in the last year, and unmaintained servers fall behind it.
  • A community or DIY server hands that maintenance burden to your team; managed hosting keeps it on ours.
  • Pricing starts at $500 per month for a standard single-tool connector, backed by the Stay-Live Guarantee.
  • Access stays revocable at all times: remove the connector or revoke the OAuth grant and it stops immediately.

What does managed MCP server hosting include?

Managed MCP server hosting includes running the server on our infrastructure, monitoring it, keeping OAuth tokens healthy, fixing the connector when the underlying provider changes its API, and migrating it as the MCP specification evolves. Your team adds the connector in Claude and uses it; everything underneath is our job.

Hosting and maintenance come bundled as a single monthly plan, from $500 per month for a standard single-tool connector. The pricing page has the full tier breakdown, and the build fee that precedes it is covered on the MCP server development page.

Why do MCP servers need ongoing maintenance?

MCP servers need maintenance because both ends of the connection keep moving. The MCP specification is young and has shipped multiple revisions in the last year, so servers that stand still fall behind what clients expect. Meanwhile the provider's own API drifts: fields rename, endpoints deprecate, auth requirements tighten, and tokens expire.

Neither kind of change announces itself to your team. A connector that worked in January quietly degrades: a write action starts failing, a token refresh stops succeeding, a schema change makes Claude misread a field. Maintenance is the difference between a connector that keeps earning its place in your workflow and one that gets abandoned the first week it misbehaves. That is also why our process treats maintenance as part of the engagement rather than an add-on.

Managed hosting vs self-hosting a community MCP server?

Self-hosting a community MCP server is free and fine for experiments, but your team inherits the whole lifecycle: running it, securing credentials, patching it when the API or the spec changes, and debugging it when it breaks. Managed hosting moves that lifecycle to a party whose job is keeping it alive.

There is also a scope difference: a community server ships the tools its author needed, not necessarily the ones you need, and write actions in particular deserve the scoped, approval-gated design described on the security page. The custom connector vs building it yourself comparison walks through the in-house version of the same trade-off.

What happens when something breaks?

We fix it, on our clock. That commitment has teeth: under the Stay-Live Guarantee, if a vendor update ever breaks your connector while you are on maintenance and we have not restored it within two business days, that month of maintenance is on us. You never file a ticket into a void.

Hosting is half the picture

Managed hosting is the ongoing half of an engagement that starts with a build. If you do not have a connector yet, scope one in the build wizard or read how the Claude connector development side works. Every connector we host ships with OAuth as your own account, separated read-write tools, and approval gating on delete and send.

Frequently asked questions

How much does managed MCP server hosting cost?
Hosting and maintenance for a standard single-tool connector is $500 per month. Niche or heavily customized tools run $800 to $1,200 per month, and bespoke or on-prem systems run $1,500 to $3,000 per month, reflecting the extra infrastructure and upkeep those builds carry. The full breakdown is on the pricing page.
Do you offer an uptime SLA?
We do not publish an uptime percentage. What we commit to is the Stay-Live Guarantee: while you are on maintenance, if a vendor update ever breaks your connector and we have not restored it within two business days, that month is on us. It is a concrete promise rather than a decorative number.
Can you host an MCP server you did not build?
Our managed hosting is part of the build engagement: we host and maintain connectors we built, because that is the only way we can stand behind how they behave. If you have an existing server that is not holding up, we can rebuild it as a supported connector and take it over from there.
What happens to my credentials while you host the server?
The connector authenticates as your own account through OAuth, and we manage the tokens it needs to keep running, stored securely and used only for the actions you scoped. You can revoke the grant from your tool's account settings at any time, which immediately cuts the connector's access. The security page covers the full model.
What if I want to stop?
You can stop whenever you want. Remove the connector in Claude or revoke the OAuth grant and access ends immediately. Nothing about the hosting arrangement locks you in, and there is no long-term contract to buy out of.
Does maintenance include changing what the connector does?
Keeping the scoped actions working is always included: API fixes, token health, and spec migrations. When your tool changes in ways you want Claude to use, we extend the connector as part of the ongoing relationship. A large expansion of scope, like a whole new set of write actions, is scoped and priced like a small build.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us