MCP Server
Your AI coding agent,
now connected.The SelfHost MCP server gives Claude, Cursor, and VS Code direct access to your database infrastructure. Provision, scale, monitor, and backup – without leaving your editor.
What we believe
The SelfHost
MCP Server.
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.
Operate through AI
SelfHost exposes your database infrastructure through MCP, so AI can provision, scale, monitor, and manage your databases.
How it connects
76 tools, 8 modules
Everything your
infrastructure needs.
Create, scale, reboot, fork, and delete database instances. Platform-managed or BYOC.
$ 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
Quickstart
Three steps,
that's it.
$ npm install -g @selfhost.dev/mcp-server
✓ Installed @selfhost.dev/mcp-server@1.2.0
# 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 divyam@selfhost.dev
✓ Organization: Swatantra Cloud Systems
✓ 76 tools registered. Ready.
What we believe
Your data stays
where you put it.
The MCP server runs on your machine. It talks to the SelfHost API to manage infrastructure – it never connects to your databases directly. Credentials are stored locally with owner-only permissions.
Runs locally on your machine
Service process stays in your terminal, not our cloud
No database connection
Manages infrastructure via API – never touches your data
Destructive ops require confirmation
delete, stop, reboot – Claude will always ask before acting
Credentials stored with chmod 600
~/.selfhost/credentials.json – owner-only access