The Short Answer
If you’re a solo founder or small team who needs an MCP server working across multiple devices or shared with anyone else, a managed gateway saves you real time and likely pays for itself in the first week. Self-hosting only wins when you already have DevOps skills, you’re connecting to a local-only database, and you’re comfortable treating the server as something you maintain forever.
MCP — the Model Context Protocol — is now the standard way AI agents connect to your data and tools. That means choosing how to host your MCP server is a real infrastructure decision, not a coding exercise. Here’s what actually differs between the two approaches, grounded in how small teams use these tools day to day.
What Each Approach Actually Looks Like
Self-hosted: you run it on your own machine or server
You download an open-source MCP server, write a JSON config file, add your database connection string to a .env file, and point your AI client at it. The software itself is free. You own every line of the deployment.
This works fine for a developer running Claude on a single laptop, connected to a local PostgreSQL database. It’s a reasonable choice if you like owning your stack and don’t mind troubleshooting a broken config at midnight.
But “free” doesn’t mean costless. You handle updates, security patches, Docker dependency upgrades, and any outage when your laptop sleeps or your VPS crashes. The open-source ecosystem around MCP is solid and growing, but none of those servers come with built-in audit logs, read-only enforcement, or credential encryption. You build or bolt those on yourself.
Managed: a service runs it for you
You paste your database credentials into a secure dashboard, get back a single HTTPS endpoint URL, and drop that URL into your AI client. The gateway handles the connection, encryption, query execution, and logging. Some platforms enforce read-only access by default and keep every query in an audit trail. Your credentials live encrypted on their infrastructure, not in a plaintext .env file on your laptop.
Setup takes under a minute. The trade-off is a monthly fee — typically priced for indie developers and small teams rather than enterprise budgets — and depending on one provider for uptime and security.
The Real Trade-offs, Side by Side
Setup and daily friction
Self-hosted requires 30 to 60 minutes per device you want to connect, plus time to debug config issues. If you switch laptops or share access with a teammate, someone rebuilds the setup from scratch. Managed hosting gives you one URL that works everywhere, instantly.
Security: where self-hosted quietly gets expensive
This is the trade-off most founders miss. A .env file with your production database credentials sitting on a developer’s machine is a real exposure. If that laptop gets stolen, lost, or synced to an unsecured cloud drive, your credentials are out there in plaintext. Managed gateways encrypt credentials at rest and never store a local copy.
Self-hosted also means you’re responsible for SQL injection protection, PII scanning, rate limiting, and multi-tenant isolation if you ever share the server. A raw MCP server has no concept of user identity or access control — every caller gets the same capabilities. Building a governance layer around that takes days to weeks, and keeping it secure across a growing fleet of servers is where the real engineering cost lives.
Audit trails and compliance
If you need to know which queries ran, when, and by whom — whether for internal accountability or a customer question — managed gateways log every operation by default. Self-hosted gives you nothing unless you build it yourself, which is rarely a small task.
Multi-device and team access
Self-hosted MCP servers tied to a local machine vanish when that machine goes to sleep. For autonomous agents that need persistent context across sessions — tracking file changes, maintaining state, coordinating across multiple agents — a hosted server is the difference between a prototype and something that actually works in production. Managed hosting also lets a whole team share one configuration from a central dashboard instead of each person managing their own copy.
The cost question, honestly
Self-hosted looks like $0. A VPS runs $6 to $24 a month depending on specs and provider. LLM API costs are separate and apply either way — every tool call, every task execution burns tokens regardless of where the MCP server lives.
Managed hosting typically runs $19 a month or around $149 a year. But the question isn’t just the monthly price. An hour of your engineering time — pulling a server down at 2 AM, debugging a TLS certificate, writing a custom governance layer — costs far more than a year of managed hosting. Teams that count only server fees consistently underestimate their total cost by three to five times once maintenance labor is included.
For most non-technical founders, the managed option is the faster path to a working agent. For developers who already run their own infrastructure and need deep customization, self-hosting still earns its keep.
When to Choose Each Option
Choose self-hosted when:
- You’re comfortable with terminal, JSON configs, and environment variables
- You’re connecting only to a local database that isn’t exposed to the internet
- You use one machine and don’t need audit logs or team sharing
- Zero recurring cost matters more to you than saved time
- You have the DevOps capacity to patch, monitor, and maintain it long-term
Choose managed hosting when:
- You work across multiple devices and want the same setup everywhere
- You’re connecting to a production database and want read-only enforcement without configuring it yourself
- You need an audit trail of queries for accountability or compliance
- You’re sharing database access with a team
- You’re not a developer and don’t want to touch config files
- You value shipping fast over owning every line of infrastructure
What to Look for in a Managed MCP Gateway
If you go the managed route, here’s what actually matters:
- Credential encryption: your database passwords should be encrypted at rest, never stored in plaintext
- Read-only enforcement: can you lock the connection to read-only by default, without writing custom SQL policies?
- Audit logging: are queries logged with timestamps and context, or do you get nothing?
- Multi-device access: does one URL work across your laptop, desktop, and team members’ machines?
- Database support: does it cover the databases you actually use — PostgreSQL, MySQL, Supabase, etc.
- Pricing clarity: is there a free tier for prototyping, and are the paid limits clear before you commit?
Frequently Asked Questions
Can I mix self-hosted and managed servers? Yes. Many teams run simple, low-sensitivity connections self-hosted and put production databases behind a managed gateway. MCP clients can connect to multiple servers simultaneously, so you’re not locked into one approach.
Does managed hosting slow down my agent? Generally no. Managed gateways use the same SSE or HTTP transport as local servers, and latency is usually dominated by the LLM response time, not the MCP connection. The persistence and uptime benefits typically outweigh any negligible network overhead.
What happens if the managed service goes down? This is a valid risk. Any hosted service can have outages. If MCP access is critical to your workflow, keep a self-hosted fallback ready for your most important connections, or choose a provider with a clear uptime track record.
Is self-hosting safer because my data never leaves my server? Not necessarily. A misconfigured VPS with a public database port is often riskier than a managed gateway with encrypted credentials and enforced access policies. Security comes from good configuration, not just physical control of the hardware.
Can I migrate from self-hosted to managed later? Most managed gateways support importing your database connection details. Migration is usually a matter of pointing your client at the new endpoint URL and updating your credential storage — not a data migration project.
Bottom Line
Self-hosted and managed MCP hosting solve the same problem with different trade-offs. Self-hosting gives you control and zero recurring fees, but the hidden costs — maintenance labor, security responsibility, setup friction across devices — add up fast. Managed hosting trades a modest monthly fee for speed, security, auditability, and team access.
For most indie founders and small teams, managed hosting is the pragmatic choice. The tool should remove pain, not create it. If you’re spending more time configuring your MCP server than building your product, the answer is probably already clear.
