happypod-mcp
OfficialAllows provisioning and managing managed Redis databases through Happy Pod, including creating databases, retrieving connection details, listing databases, and deleting them.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@happypod-mcp why is checkout slow in production?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Happy Pod MCP server and skills
Use Happy Pod from your AI coding tool: ship an app, add a database, start a GPU pod, find out why production is slow and fix it, all by asking in plain language.
MCP server (
happypod-mcp): 33 tools over the Happy Pod API. Works in Claude Code, Codex, Cursor, VS Code, Windsurf, Claude Desktop and any MCP client.Skills (
skills/): playbooks so the agent works the way Happy Pod expects (price first, confirm before deleting, read the logs when a deploy fails):happypod: access, safety rules, which skill to use.happypod-ship: app pods from a repo or image, managed Postgres and Redis, custom domains, GPU pods.happypod-ops: diagnose, logs and metrics, roll back, restart, scale, keep the bill low.
Install
Claude Code (plugin: server and skills together)
/plugin marketplace add happy-pod/mcp
/plugin install happypod@happypodThen give it your key (Settings → API keys at happypod.io) before starting Claude Code:
export HAPPYPOD_API_KEY=hp_...Any MCP client (local server)
git clone https://github.com/happy-pod/mcp happypod-mcp{
"mcpServers": {
"happypod": {
"command": "node",
"args": ["/path/to/happypod-mcp/dist/stdio.js"],
"env": { "HAPPYPOD_API_KEY": "hp_..." }
}
}
}dist/stdio.js is a single bundled file: no npm install needed to run it.
Try it without an account
Set HAPPYPOD_MODE=demo (or pass --demo). Every tool then talks to a built-in simulator: a sample project, deployments that build and go live (or fail with a real-looking error you can fix), logs, metrics and example prices. Nothing leaves your machine and nothing is billed.
HAPPYPOD_MODE=demo node dist/stdio.jsRelated MCP server: helipod-mcp
Configuration
Variable | |
| Your API key from happypod.io → Settings → API keys |
| Optional, another API base URL. Default |
|
|
Tools
Group | Tools |
Account and catalogue |
|
Projects |
|
Ship |
|
Operate |
|
Variables and domains |
|
Databases |
|
Every tool that changes something is marked destructive, so MCP clients ask before running it. Paid tools take dryRun: true (returns the price, changes nothing) and an idempotencyKey (a retry never creates twice). Deletes need the resource's exact name in confirm. Errors come back as { status, code, error, details } so the agent can act on them.
Things to ask
"Ship this repo to Happy Pod with a Postgres database."
"Why is checkout slow in production?"
"The last deploy broke the login page, roll it back."
"Serve Llama 3.1 8B on the cheapest GPU and stop it when I'm done."
"What am I paying for this month, and what can I turn off?"
Develop
npm install
npm test # tool catalogue, demo flows and the bundled stdio server
npm run build # bundles src/stdio.ts into dist/stdio.jsThe API contract the server expects is in docs/API.md.
License
MIT
Available Tools
33 toolsadd_domainAdd custom domainADestructive
Attach a custom domain to a pod's public port. Returns the DNS record the user must create (CNAME for subdomains, A/AAAA for an apex). HTTPS is issued automatically once DNS points here.
Inputs: podId (required), hostname (required).
create_databaseCreate databaseADestructive
Create a managed Postgres or Redis database with daily backups. The hobby plan is free. dryRun first for paid plans. Then pass its connection URL to the app as a secret (get_database_connection + set_env).
Inputs: name (required), engine (required), projectId (required), plan, +3 more.
create_gpu_podCreate GPU podADestructive
Start a GPU pod from a container image (inference servers, notebooks, fine-tuning, batch jobs). Billed per hour while running. ALWAYS dryRun first and tell the user the hourly price; stop it with stop_pod when the job is done.
Inputs: name (required), image (required), gpuType (required), projectId (required), +8 more.
create_podCreate podADestructive
Create an app pod and start its first deployment. Source is a Git repository (built automatically: a Dockerfile is used when present, otherwise the stack is detected) or a container image. ALWAYS call with dryRun: true first, tell the user the price, and create only after a clear yes. Then poll get_deployment until success or failed.
Inputs: name (required), projectId (required), env, repo, +10 more.
create_projectCreate projectBDestructive
Create an empty project (free). One project per app is a good default.
Inputs: name (required), idempotencyKey.
delete_databaseDelete databaseADestructive
Delete a database and all its data and backups. Irreversible. Only after the user agrees; confirm must be the database's exact name.
Inputs: confirm (required), databaseId (required).
delete_podDelete podADestructive
Delete a pod, its deployments, domains and volumes. Irreversible. Only after the user agrees; confirm must be the pod's exact name.
Inputs: podId (required), confirm (required).
delete_projectDelete projectADestructive
Delete an EMPTY project. Irreversible. Refused with 409 PROJECT_NOT_EMPTY while pods or databases remain. Only after the user agrees; confirm must be the project's exact name.
Inputs: confirm (required), projectId (required).
deploy_podDeploy podADestructive
Build and roll out the pod again from its source (latest commit of the branch, or the image tag). Needed after changing variables. Zero-downtime: the old version serves until the new one is healthy.
Inputs: podId (required), idempotencyKey.
diagnose_podDiagnose podARead-onlyIdempotent
Happy Pod's own health check for a pod: reads the last deployment, recent error logs and metrics, and returns findings (severity, evidence, suggested fix). Start here when the user says something is broken or slow.
Inputs: podId (required).
get_database_connectionDatabase connectionARead-onlyIdempotent
Host, port, database and user, plus the connection URL with the password masked. reveal: true returns the real URL: use it only to pass into set_env secrets, never print it to the user.
Inputs: databaseId (required), reveal.
get_deploymentGet deploymentARead-onlyIdempotent
One deployment's status: queued, building, deploying, success or failed. Poll every few seconds after create_pod or deploy_pod; builds take one to five minutes.
Inputs: deploymentId (required).
get_deployment_logsDeployment logsARead-onlyIdempotent
Build and start-up log of a deployment. Read it when a deployment failed: the cause is usually a missing variable, the wrong port or a build error.
Inputs: deploymentId (required), tail.
get_podGet podARead-onlyIdempotent
One pod in full: source, size, replicas, region, ports, URL, domains, status and the last deployment.
Inputs: podId (required).
get_pod_logsPod logsBRead-onlyIdempotent
Runtime logs of a running pod across replicas.
Inputs: podId (required), tail, level, since.
get_pod_metricsPod metricsBRead-onlyIdempotent
CPU, memory, requests per second, error rate and p95 latency over a window, per replica and in total.
Inputs: podId (required), window.
list_databasesList databasesCRead-onlyIdempotent
Managed databases in a project: engine, plan, status, region.
Inputs: projectId (required).
list_deploymentsList deploymentsARead-onlyIdempotent
A pod's deployments, newest first: id, status, commit or image, start and finish time. Use it to pick a deploymentId for rollback_pod.
Inputs: podId (required), limit.
list_domainsList domainsBRead-onlyIdempotent
A pod's domains with DNS and certificate status (pending_dns, issuing, active).
Inputs: podId (required).
list_envList variablesBRead-onlyIdempotent
A pod's environment variables. Secret values come back masked.
Inputs: podId (required).
list_gpu_typesList GPU typesARead-onlyIdempotent
GPU types for GPU pods: VRAM, hourly USD price and the regions with free capacity right now.
Inputs: region.
list_podsList podsBRead-onlyIdempotent
Pods in a project: app pods (web apps, APIs, workers) and GPU pods, with status, size, replicas, URL and the last deployment.
Inputs: projectId (required).
list_projectsList projectsARead-onlyIdempotent
Projects this key can reach, each with its pod and database counts. Start here to find a projectId.
Inputs: no named parameters.
list_regionsList regionsARead-onlyIdempotent
Regions where pods and databases can run, with their city and whether GPUs are available there. Pick the one closest to the app's users.
Inputs: no named parameters.
list_sizesList pod sizesARead-onlyIdempotent
CPU pod sizes (vCPU, memory, hourly and monthly USD price). Start small: most vibe-coded apps run on small.
Inputs: no named parameters.
restart_podRestart podADestructiveIdempotent
Restart the running replicas without rebuilding. Brief interruption per replica.
Inputs: podId (required).
rollback_podRoll back podADestructive
Put an earlier successful deployment back live (no rebuild). The quickest fix when a new deploy broke the app.
Inputs: podId (required), deploymentId (required).
scale_podScale podADestructiveIdempotent
Change a pod's size and/or replica count. dryRun: true first, show the user the current and new monthly price, apply after a clear yes.
Inputs: podId (required), size, dryRun, replicas.
set_envSet variablesADestructiveIdempotent
Create or update variables. Put credentials in secrets. Changes apply on the next deploy: call deploy_pod afterwards.
Inputs: podId (required), env, secrets.
start_podStart podADestructiveIdempotent
Start a stopped pod again. Billing resumes.
Inputs: podId (required).
stop_podStop podADestructiveIdempotent
Stop a pod (billing for compute stops; volumes are kept). GPU pods should be stopped as soon as their job is done.
Inputs: podId (required).
unset_envRemove variableBDestructiveIdempotent
Remove one variable. Applies on the next deploy.
Inputs: key (required), podId (required).
whoamiWho am IARead-onlyIdempotent
The account behind the API key: name, plan, credit balance (USD), spend this month and the key's scope. Call it first in a session. mode "demo" means the built-in simulator, not a real account.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 33 tools
Most tools map cleanly to a unique resource and action, with strong descriptions explaining adjacent pod lifecycle operations. A few could be confused at a glance—start_pod/restart_pod/deploy_pod/rollback_pod and create_pod/create_gpu_pod—but the descriptions usually disambiguate.
The set follows a very consistent snake_case verb_noun pattern: list_pods, get_pod, create_database, delete_project, set_env, etc. whoami is the only exception, but it is a conventional standalone command and does not undermine the pattern.
33 tools is heavy for an agent-facing MCP surface, even for a broad PaaS. Most tools are genuinely distinct, but several pod lifecycle actions could potentially be consolidated, making this borderline rather than clearly excessive.
The core deployment lifecycle is well covered: projects, pods, GPU pods, env vars, domains, databases, deployments, logs, metrics, and diagnostics. Notable gaps remain around domain deletion, database resize/backup-restore, and deployment cancellation, but core workflows are usable.
Maintenance
Related MCP Connectors
Deploy and run your apps by asking your AI: services, Postgres, logs, traces, rollbacks, costs.
Deploy local apps, add managed Postgres, and inspect logs from your AI coding agent.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to create projects, deploy files, container images, or Git repositories, attach domains, set write-only secrets, add Postgres, read logs, metrics, and failure summaries, and roll back.19 npmApache 2.0
helipod-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to deploy apps and databases, run VPS servers, buy domains and edit DNS, and send email through natural-language requests across Container, VPS, Domain, and Email APIs.350 npmMIT
Roar AI MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to deploy and manage hosted apps from git repos, read logs, add Postgres databases and domains, manage API keys and budgets, and send requests to 200+ AI models. Connects over remote Streamable HTTP with OAuth sign-in, so users need no API keys, installs, or local server.MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.MIT