Railpush
Sends push notifications and alerts across multiple platforms effortlessly.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Whoami: Get the currently authenticated user's profile — name, email, workspace, and role. Useful for verifying API key validity and checking permissions.
- Get Api Version Info: Get API version metadata (current version, supported pins, and pinning headers/query parameters).
- Get Api Version Changelog: Get API version changelog entries used for compatibility planning and migrations.
What data it sees
Do you need an account
No: the server works without sign-in
Sends push notifications and alerts across multiple platforms effortlessly. Streamlines communication by managing messaging workflows through a unified interface. Enables real-time updates for development and monitoring tasks.
How to connect
How to connect Railpush to Claude
The server address to paste into Claude settings:
https://railpush-mcp--railpush.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Railpush to ChatGPT
The server address to paste into ChatGPT settings:
https://railpush-mcp--railpush.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Railpush to Cursor
The server address to paste into Cursor settings:
https://railpush-mcp--railpush.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (60)
Raw names from tools/list. Only developers need these.
| whoami | Get the currently authenticated user's profile — name, email, workspace, and role. Useful for verifying API key validity and checking permissions. |
| get_api_version_info | Get API version metadata (current version, supported pins, and pinning headers/query parameters). |
| get_api_version_changelog | Get API version changelog entries used for compatibility planning and migrations. |
| get_rate_limit | Get current API rate-limit state for this API key (limit, remaining, reset_at, window). |
| list_services | List services in the workspace with optional server-side filters (type/status/runtime/plan/name/repo/project/query/suspended). Supports cursor pagination via limit/cursor. |
| get_service | Get full details of a service by ID, including its configuration, status, public URL, and deploy settings. |
| create_service | Create a new service. Specify at minimum name + type. The service can be a web server, worker, cron job, or static site. Provide repo_url to deploy from a Git repo. |
| clone_service | Clone an existing service into a new service with optional configuration overrides. Optionally copies env vars/secrets from the source service. |
| update_service | Update a service's configuration. Only provided fields are changed. Use this to change branch, build/start commands, scaling plan, port, project assignment, and more. |
| get_service_retention | Get retention policy for service logs. Build log retention is enforced; runtime/request retention values are stored for policy tracking. |
| set_service_retention | Update service log retention windows. Values accept day numbers (e.g. 30) or strings like 30d, 12w, 6m, 1y. |
| get_service_mtls | Get per-service mTLS policy configuration for internal service-to-service traffic. |
| set_service_mtls | Configure per-service mTLS policy. strict mode enforces service allowlist via network policy; permissive mode stores policy without strict deny enforcement. |
| get_service_access_control | Get ingress access-control policy for a service (IP allowlist/blocklist mode, rules, and active CIDRs). |
| set_service_access_control | Configure ingress IP access control for a service. Supports allowlist/blocklist modes, CIDR rules, optional expiry, and custom deny response. |
| list_service_access_control_log | List recent access-control policy change events for a service. |
| delete_service | Delete a service using a safeguarded flow. First confirmation soft-deletes the service into a 72-hour recovery window. Optional hard_delete=true is only for permanent deletion after that window. |
| restore_service | Restore a soft-deleted service from the recovery window. Restored services come back suspended and must be resumed to run. |
| restart_service | Restart a running service. The existing containers are stopped and new ones started with the current image. |
| suspend_service | Suspend a service, stopping all its containers. The service remains configured and can be resumed later. |
| resume_service | Resume a suspended service, triggering a new deploy. |
| search_services | Search and filter services. All filters are optional and combined with AND. Name filter uses substring match. Supports cursor pagination via limit/cursor. |
| search_workspace_resources | Search services, databases, and key-value stores in one call using a workspace-scoped query. |
| get_workspace_topology | Return a dependency graph for a workspace (nodes + edges) covering services, databases, and key-value stores. |
| get_service_dependencies | Return databases, key-value stores, and services a service depends on (detected via explicit links and env-var references). |
| get_database_connected_services | List services connected to a database, including the env var / link source used to detect each connection. |
| get_database_impact | Estimate blast radius for a database by listing affected services if that database becomes unavailable. |
| bulk_update_services | Apply the same service configuration updates to multiple services in one API call. Returns per-service status and errors. |
| bulk_restart | Restart multiple services at once. Returns results for each service. |
| bulk_deploy | Trigger deploys for multiple services at once. Returns results for each service. |
| bulk_set_env_vars | Update environment variables for multiple services in one API call. Supports merge mode (upsert/delete) and replace mode. |
| bulk_suspend | Suspend multiple services at once. Returns results for each service. |
| bulk_resume | Resume multiple suspended services at once. Returns results for each service. |
| trigger_deploy | Trigger a new deploy for a service. Optionally specify a commit SHA or branch. The deploy builds the image from the repo and rolls it out. |
| list_deploys | List deploy history for a service with optional status/branch/time filtering. Supports cursor pagination via limit/cursor. |
| wait_for_deploy | Block until a deploy reaches a terminal state (live/failed/canceled) or timeout expires. |
| get_deploy | Get detailed information about a specific deploy, including build log, status, timing, and any Dockerfile override. |
| rollback_deploy | Rollback a service to a previous deploy. Creates a new deploy using the image from the specified deploy ID. |
| get_deploy_queue_position | Check a deploy's position in the build queue, including estimated wait time until execution starts. |
| enable_github_actions_deploy_gate | Enable GitHub Actions-gated auto-deploy for a service. Ensures auto_deploy is enabled and ignores push webhooks for this service until a successful workflow_run event is received. |
| disable_github_actions_deploy_gate | Disable GitHub Actions-gated auto-deploy for a service and return to push-webhook based auto-deploy behavior. |
| get_github_actions_deploy_gate | Get GitHub Actions deploy-gate status for a service, including effective deploy mode and workflow allowlist. |
| set_deploy_automation_mode | Set a service deploy automation mode: off, push, or GitHub Actions workflow-success gated deploys. Optionally provide workflow allowlist for workflow_success mode; if omitted, existing workflow allowlist is preserved. |
| set_github_actions_deploy_workflows | Set or clear the workflow allowlist used by GitHub Actions-gated deploys for a service. This updates allowlist env vars only and does not change deploy mode. |
| list_env_vars | List environment variables for a service. Secret values are masked. Supports cursor pagination via limit/cursor. |
| set_env_vars | Set environment variables for a service. This is a bulk replace operation — provide all env vars the service should have. Existing vars not in the list are removed. To perform a destructive replace, set confirm_destructive=true. Use upsert_env_vars for additive updates. |
| upsert_env_vars | Add or update environment variables for a service WITHOUT removing existing vars. Unlike set_env_vars (which replaces everything), this is additive — keys not in the list are left untouched. Optionally specify keys to delete. |
| list_service_disks | List persistent disks attached to a service. Services may have at most one attached disk. |
| set_service_disk | Create or replace a service disk attachment. Requires a single-instance service; redeploy is required after changes. |
| delete_service_disk | Delete the persistent disk attachment from a service. Redeploy is required after deletion. |
| list_custom_domains | List custom domains configured for a service. Supports cursor pagination via limit/cursor. |
| add_custom_domain | Add a custom domain to a service. You must point the domain's DNS (CNAME) to the service's public URL for verification and TLS provisioning. Optionally set redirect_target to make the domain 301-redirect to another URL (e.g. redirect apex to www). |
| delete_custom_domain | Remove a custom domain from a service. |
| list_rewrite_rules | List rewrite/proxy rules for a service. Rewrite rules let you route specific URL paths (e.g. /api/*) from one service to another service's backend. |
| add_rewrite_rule | Add a rewrite/proxy rule to a service. Routes requests matching source_path on this service to dest_path on the destination service. Supports wildcard paths (e.g. /api/*). |
| delete_rewrite_rule | Delete a rewrite/proxy rule from a service. |
| list_databases | List managed PostgreSQL databases in the workspace with optional server-side filters. Supports cursor pagination via limit/cursor. |
| create_database | Create a new managed PostgreSQL database. |
| get_database | Get database details and redacted connection strings (passwords are not returned by this endpoint). |
| reveal_database_credentials | Reveal plaintext credentials for a database. Use only when absolutely required; output may be stored in logs/conversation history. |