# RailPush MCP Server
276 MCP tools for deploying and managing cloud infrastructure
Connect Claude, Cursor, Windsurf, or any MCP client to a full PaaS platform.
## What can your agent do?
With 276 tools, your AI agent gets full control of cloud infrastructure:
| Category | Tools | Examples |
|----------|-------|---------|
| **Services** | 35+ | Create, deploy, restart, scale, clone, suspend web services |
| **Deploys** | 15+ | Trigger builds, rollback, blue-green, canary, PR previews |
| **PostgreSQL** | 20+ | Create databases, run queries, backup, restore, PITR, replicas |
| **MySQL** | 7 | Create, manage, reveal credentials, delete MySQL 8.0 instances |
| **MongoDB** | 7 | Create, manage, reveal credentials, delete MongoDB 7.0 instances |
| **Redis** | 7 | Create, manage, reveal credentials, delete Redis instances |
| **Meilisearch** | 7 | Create, manage full-text search instances |
| **Object Storage** | 7 | Create, manage S3-compatible MinIO instances |
| **Environment** | 15+ | Set/get env vars, manage env groups, bulk operations |
| **Domains** | 15+ | Custom domains, domain registration, DNS records |
| **Scaling** | 5+ | Autoscaling policies, manual scaling |
| **Logs & Metrics** | 10+ | Query logs (Loki), metrics (Prometheus), log drains |
| **Blueprints** | 5+ | IaC — define and sync infrastructure from YAML |
| **Networking** | 5+ | WAF rules, network policies |
| **Billing** | 5+ | Usage, invoices, plan management |
| **AI Fix** | 2 | Auto-diagnose and fix broken deploys |
## Machine-readable catalog
For directories and integrations, this repo includes a generated machine-readable catalog of all 276 hosted tools:
- [`mcpnest-catalog.json`](./mcpnest-catalog.json)
Each entry includes:
- `name`
- `description`
- `category`
- `github_url`
- `endpoint_url`
- `tags`
- `language`
All catalog entries point to the same hosted RailPush MCP endpoint:
- `https://mcp.railpush.com/mcp`
## Quick start
### Hosted server (recommended)
No installation needed. Connect directly:
```json
{
"mcpServers": {
"railpush": {
"url": "https://mcp.railpush.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
```
**Claude Code CLI:**
```bash
claude mcp add railpush --url https://mcp.railpush.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
```
**Cursor:** Settings → MCP → Add Server → paste the JSON above.
### Local stdio server
For air-gapped or custom setups:
```bash
cd mcp && npm install && npm run build
```
```json
{
"mcpServers": {
"railpush": {
"command": "node",
"args": ["/path/to/mcp/build/index.js"],
"env": {
"RAILPUSH_API_KEY": "your-api-key",
"RAILPUSH_API_URL": "https://railpush.com"
}
}
}
}
```
## Example: deploy a full-stack app
Tell your agent:
> "Create a Node.js web service called 'my-api' on the starter plan, add a PostgreSQL database, set DATABASE_URL as an env var, and deploy from my GitHub repo."
The agent will call:
1. `create_service` → provisions the service
2. `create_database` → provisions PostgreSQL
3. `reveal_database_credentials` → gets the connection string
4. `set_env_var` → sets DATABASE_URL
5. `trigger_deploy` → builds and deploys from Git
All in one conversation. No YAML, no CLI, no dashboard clicking.
## Transports
| Transport | URL | Use case |
|-----------|-----|----------|
| **Streamable HTTP** | `https://mcp.railpush.com/mcp` | Recommended — modern MCP clients |
| **SSE (legacy)** | `https://mcp.railpush.com/sse` | Older clients that only support SSE |
## Authentication
All requests require an API key. Get one from the [RailPush dashboard](https://railpush.com) → Settings → API Keys.
Pass it as:
- `Authorization: Bearer YOUR_API_KEY` header (hosted server)
- `RAILPUSH_API_KEY` environment variable (local stdio)
## Links
- 🌐 [RailPush](https://railpush.com) — the platform
- 📖 [Documentation](https://railpush.com/docs) — full docs
- 💰 [Pricing](https://railpush.com/pricing) — free tier available
- 📋 [Changelog](https://railpush.com/changelog) — what's new