MCP Server

The Selfhost.dev MCP Server:

Your AI DevOps Engineer.

The Selfhost.dev MCP server gives Claude, Cursor, Windsurf, and VS Code direct access to everything your product needs: managed PostgreSQL, MySQL, Redis, and ClickHouse on AWS, plus MongoDB in your projects, app and API deployments from GitHub, and Supabase templates. Provision, scale, monitor, back up, restore to any second, deploy, and manage domains, all without leaving your editor. 150+ production-ready tools across 23 modules.

And because every action runs against prepaid credits that pause at a $0 balance, no agent can run up a surprise bill. No charge in hindsight, no ghost compute.

$ npx @selfhost.dev/mcp-server
Start free Try the live demo View on npm
Works with
Claude
Cursor
Windsurf
VS Code
+ any MCP client
claude - selfhost workspace

What we believe

The Selfhost.dev
MCP Server.

MCP, explained simply

One protocol. Total control.

MCP is the standard that lets your AI tools work with the system through a controlled interface, enabling actions, not direct access.

AI infrastructure management tools

Operate through AI

Selfhost.dev exposes your whole platform through MCP: databases, projects, deployments, domains, and billing, so AI can provision, scale, monitor, and manage all of it. The deepest first-party infrastructure MCP server in the category - see how competitors compare.

How it connects

AI Client Claude · Cursor · Windsurf
MCP protocol
SELFHOST.DEV MCP SERVER @selfhost.dev/mcp-server
list_instances restore_pitr
connection...
Your backend Databases · Projects
BYOC safe encrypted

150+ MCP tools, 23 modules

Everything your
infrastructure needs.

Create, scale, reboot, and delete managed PostgreSQL, MySQL, Redis, and ClickHouse instances on AWS, with forking on every engine. Platform-managed or BYOC.

mcp · instances

$ Create a Postgres 18 in us-east-1 with 4GB RAM

⚡ calling create_instance ...

✓ Instance created: prod-pg-18

  us-east-1 · t4g.medium · 4 GB · PostgreSQL 18

  Status: launching

One prompt, end to end

One prompt.
The whole deploy.

Ask once. Your agent provisions the database, wires the connection string, deploys from GitHub, and brings the domain live, calling the right tools in order and confirming each step.

mcp · agent

> Spin up a Postgres DB for acme/web, wire it into the app, and ship it to production.

⚡ instances.create

✓ prod-db ready · us-east-1 · t4g.small · PostgreSQL 18

⚡ env.set DATABASE_URL → acme-web

✓ wired · encrypted at rest

⚡ github.deploy acme/web @ main

✓ build passed (nixpacks) · 38s

⚡ domains.attach app.acme.com

✓ DNS verified · SSL issued

✓ Live at https://app.acme.com (42s)

One prompt. Database provisioned, config wired, app deployed, domain live. Destructive steps still ask first, and every action bills against prepaid credits, so nothing runs up a surprise.

Quickstart

Three steps,
that's it.

mcp · instances

$ npm install -g @selfhost.dev/mcp-server

✓ Installed @selfhost.dev/mcp-server

# Add to your MCP config:

# "selfhost": { "command": "npx", "args": ["@selfhost.dev/mcp-server"] }

$ npx @selfhost.dev/mcp-server

Opening browser for authentication...

✓ Signed in as you@acme.com

✓ Organization: Acme Inc

✓ 150+ tools registered. Ready.

Security

Your data stays
where you put it.

The MCP server database management runs on your machine. It talks to the Selfhost.dev API to manage infrastructure - it never connects to your databases directly. Credentials are stored locally with owner-only permissions.

01

Runs locally on your machine

Service process stays in your terminal, not our cloud

02

No database connection

Manages infrastructure via API - never touches your data

03

Destructive ops require confirmation

delete, stop, reboot - Claude will always ask before acting

04

Credentials stored with chmod 600

~/.selfhost/credentials.json - owner-only access

Frequently Asked Questions

What is the Selfhost.dev MCP server?
The Selfhost.dev MCP server is an AI-powered toolkit with 150+ tools across 23 modules that lets you manage your whole backend from Claude, Cursor, or VS Code in natural language: managed PostgreSQL, MySQL, Redis, and ClickHouse on AWS, plus your project servers (deploys, databases, domains). It's the deepest first-party MCP in the category.
How many MCP tools does Selfhost.dev provide?
150+ tools across 23 modules. The database half covers instances, backups, PITR, database users, scaling, pooling (PgBouncer and ProxySQL), alerts, networking, engine config, credentials/BYOC, and billing. The Projects half covers projects, deployments, GitHub, project databases, services, domains, env vars, and notifications. Every tool is available on every account; Selfhost.dev is pay-as-you-go. See pricing.
Which AI tools work with the Selfhost.dev MCP server?
It works with Claude (Desktop and Code), Cursor, Windsurf, VS Code, and any MCP-compatible client. Install with npx @selfhost.dev/mcp-server, authenticate via browser, and all 150+ tools become available in your AI editor immediately.
Can I manage databases and deployments from Claude?
Yes. Ask Claude to create a Postgres, MySQL, Redis, or ClickHouse database, run backups (with restore to any second on PostgreSQL and MySQL), and tune settings, and also to create a project, deploy a GitHub repo, add a domain, or set environment variables, all in plain English. The MCP executes these through a controlled interface, with confirmation on destructive operations.
How does the Selfhost.dev MCP server compare to others?
Most MCP servers focus on one slice (database queries, or a single PaaS) with a handful of tools. Selfhost.dev provides 150+ first-party tools spanning the full lifecycle of both managed databases and app deployments. See full comparisons.
Is the Selfhost.dev MCP server safe for production?
Yes. The MCP server runs locally on your machine and communicates with the Selfhost.dev API to manage infrastructure; it never connects to your databases directly. Destructive operations (delete, stop, reboot) require explicit confirmation, and credentials are stored locally with chmod 600 owner-only permissions.
How do I install the Selfhost.dev MCP server?
Run npx @selfhost.dev/mcp-server, add it to your MCP config file, then run the server - it opens your browser for authentication. Once signed in, all 150+ tools register automatically. The entire setup takes under 2 minutes. Available on npm at @selfhost.dev/mcp-server.
How much does the MCP server cost?
The MCP server is included with every Selfhost.dev account at no extra cost, and all 150+ tools are available to everyone. Selfhost.dev is pay-as-you-go: top up credits from $5 and pay only for the resources you run, with no tiers or subscriptions. See pricing.
Can I use the MCP server with BYOC?
Yes. The MCP tools work with both platform-managed and BYOC deployments. On BYOC, the server manages your databases running in your own AWS account through the Selfhost.dev API, so you get AI-native management while keeping full infrastructure ownership.
Which clouds does the MCP server manage?
Managed PostgreSQL, MySQL, Redis, and ClickHouse run on AWS (with BYOC into your own account). Project servers run on Hetzner-backed compute for lower cost. The MCP server manages both from one place, so your AI agent provisions databases and deploys apps without you switching tools.

Try the Selfhost.dev
MCP Server today.

Available on every account
All 150+ tools, pay-as-you-go
Start free Try the live demo View on npm