Scalingo MCP by usefulapi
Server Details
Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.
- Status
- Healthy
- Uptime
- 79.6% over 55 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
TDQS
Scored across 21 tools
Each tool targets a distinct resource or action: get_app vs get_app_logs vs get_app_stats are clearly different; list_addon_providers vs list_addons differentiate available vs provisioned. Mutation tools (restart, scale, trigger_deployment, set_variables) are unique. The fallback scalingo_request is a separate generic GET. No confusion between tools.
All tools use snake_case with a verb_noun pattern (get_, list_, restart_, scale_, trigger_, set_). The only exception is 'scalingo_request' which breaks the pattern, but it is clearly documented as a power-user escape hatch. Overall very consistent.
21 tools is well-scoped for a PaaS platform covering core resources like apps, deployments, addons, domains, env variables, and collaborators. It covers the essential operations without being bloated; each tool serves a clear purpose.
The toolset is heavily read-oriented; mutations are limited to restart, scale, set_variables, and trigger_deployment. Missing CRUD for major resources: no create/delete app, add/remove collaborators, add/remove domains, provision/delete addons, or update app settings. Agents will face dead ends when needing to perform writes beyond the few covered.
Available Tools
21 toolsget_accountGet current accountRead-onlyInspect
Fetch the authenticated user's account (id, email, username, fullname, company). Scalingo API: GET /v1/users/self. Returns { user }.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_appGet an appRead-onlyInspect
Fetch a single app's details (region, stack, status, URLs, flags). Scalingo API: GET /v1/apps/{app}. Returns { app }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
get_app_logsGet recent app logsRead-onlyInspect
Fetch recent application log lines. Scalingo returns an authenticated logs_url (GET /v1/apps/{app}/logs → { logs_url }); this tool then downloads the last N lines from it (dump mode) and returns them as text. Returns { logs_url, lines }. If the follow-up download fails, only logs_url is returned so you can fetch it yourself.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| lines | No | Number of recent log lines to fetch (1-1000, default 100). |
get_app_statsGet container statsRead-onlyInspect
Real-time per-container resource stats (CPU / memory / swap usage) for an app. Scalingo API: GET /v1/apps/{app}/stats. Returns { stats: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
get_deploymentGet a deploymentRead-onlyInspect
Fetch a single deployment's details (status, git_ref, pusher, image size, timestamps). Scalingo API: GET /v1/apps/{app}/deployments/{deployment_id}. Returns { deployment }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| deployment_id | Yes | The deployment id. |
get_operationGet an operationRead-onlyInspect
Poll the status of an asynchronous operation (e.g. a scale or restart returns an operation to track). Scalingo API: GET /v1/apps/{app}/operations/{operation_id}. Returns { operation } with status pending|running|done|error.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| operation_id | Yes | The operation id (returned in the Location header of a scale/restart response). |
list_addon_providersList addon providersRead-onlyInspect
List the addon providers available on Scalingo (databases, monitoring, etc.) with their plans embedded. Scalingo API: GET /v1/addon_providers. Returns { addon_providers: [{ ..., plans: [...] }] }.
| Name | Required | Description | Default |
|---|---|---|---|
| category_id | No | Optional category id to filter providers. |
list_addonsList addonsRead-onlyInspect
List the addons (databases, services) provisioned on an app. Scalingo API: GET /v1/apps/{app}/addons. Returns { addons: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
list_app_eventsList app eventsRead-onlyInspect
List an app's activity events (deployments, scaling, restarts, collaborator changes, etc.), paginated. Scalingo API: GET /v1/apps/{app}/events. Returns { events: [...], meta: { pagination } }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| from | No | Restrict to events from the last N hours (1-72). | |
| page | No | Page number (1-based) for paginated lists. | |
| per_page | No | Entries per page (1-100). |
list_appsList appsRead-onlyInspect
List all Scalingo apps you can access in the current region. Scalingo API: GET /v1/apps. Returns { apps: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_collaboratorsList collaboratorsRead-onlyInspect
List an app's collaborators (users invited to the app) and their status. Scalingo API: GET /v1/apps/{app}/collaborators. Returns { collaborators: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
list_containersList containers (formation)Read-onlyInspect
List an app's container formation — the running process types with their amount and size (the current scaling). Scalingo API: GET /v1/apps/{app}/containers. Returns { containers: [{ name, amount, size }] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
list_deploymentsList deploymentsRead-onlyInspect
List an app's deployments (most recent first), paginated. Scalingo API: GET /v1/apps/{app}/deployments. Returns { deployments: [...], meta: { pagination } }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| page | No | Page number (1-based) for paginated lists. | |
| per_page | No | Entries per page (1-100). |
list_domainsList domainsRead-onlyInspect
List an app's custom domains and their TLS/canonical status. Scalingo API: GET /v1/apps/{app}/domains. Returns { domains: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
list_regionsList regionsRead-onlyInspect
List the Scalingo regions available to your account, each with its API/dashboard/database hosts. Useful to discover the right SCALINGO_REGION. Scalingo API: GET (auth host) /v1/regions. Returns { regions: [...] }.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_variablesList environment variablesRead-onlyInspect
List an app's environment variables. WARNING: this exposes secret VALUES (API keys, database URLs, etc.). Scalingo API: GET /v1/apps/{app}/variables. Returns { variables: [{ id, name, value }] }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). |
restart_appRestart appDestructiveInspect
MUTATES Scalingo infrastructure — restarts an app's containers. Optionally restart only specific process types via scope; omit scope to restart everything. Returns 202 Accepted (track via get_operation). Scalingo API: POST /v1/apps/{app}/restart.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| scope | No | Container types to restart, e.g. ["web","worker"]. Omit to restart all. |
scale_appScale appDestructiveInspect
MUTATES Scalingo infrastructure — sets the container formation (number and/or size of each process type). Only the container types you include are changed. Returns 202 Accepted (track via get_operation). Scalingo API: POST /v1/apps/{app}/scale.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| containers | Yes | Formation entries to apply. Each entry needs a name plus amount and/or size. |
scalingo_requestRaw read requestRead-onlyInspect
Power-user escape hatch: GET any Scalingo API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Path is taken after /v1 (e.g. "/apps/my-app/alerts"). By default hits the regional API; set on_auth_host:true for auth-host resources (regions, scm_integrations, tokens). Scalingo API: GET {path}.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | API path after /v1, starting with a slash, e.g. "/apps/my-app/notifiers". | |
| query | No | Optional query params object. | |
| on_auth_host | No | If true, target the auth host (auth.scalingo.com) instead of the regional API. |
set_variablesSet environment variables (bulk)DestructiveInspect
MUTATES Scalingo infrastructure — creates or updates environment variables in bulk (each { name, value } is created if new or updated if it exists). This usually triggers a restart to apply the new env. Names ≤64 chars, values ≤8192 chars. Scalingo API: PUT /v1/apps/{app}/variables. Returns { variables }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| variables | Yes | Environment variables to create/update. |
trigger_deploymentTrigger a deploymentDestructiveInspect
MUTATES Scalingo infrastructure — triggers a new deployment from a source archive URL (a tar.gz reachable by Scalingo). To roll back, re-deploy a previous git_ref/archive — there is no separate rollback endpoint. Scalingo API: POST /v1/apps/{app}/deployments. Returns { deployment }.
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | The app name (e.g. my-production-app) or app id (app-…). | |
| git_ref | No | Optional git reference label for the deployment (branch/tag/SHA). | |
| source_url | Yes | URL of the source archive (tar.gz) Scalingo should build and deploy. |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
21 tool updates
- Changed
get_account1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
get_app1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
get_app_logs1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
get_app_stats1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
get_deployment1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
get_operation1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_addon_providers1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_addons1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_app_events1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_apps1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_collaborators1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_containers1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_deployments1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_domains1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_regions1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
list_variables1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
restart_app1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
scale_app1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
scalingo_request1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
set_variables1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
- Changed
trigger_deployment1 field changed- changed
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
21 tool updates
- First observed
get_account - First observed
get_app - First observed
get_app_logs - First observed
get_app_stats - First observed
get_deployment - First observed
get_operation - First observed
list_addon_providers - First observed
list_addons - First observed
list_app_events - First observed
list_apps - First observed
list_collaborators - First observed
list_containers - First observed
list_deployments - First observed
list_domains - First observed
list_regions - First observed
list_variables - First observed
restart_app - First observed
scale_app - First observed
scalingo_request - First observed
set_variables - First observed
trigger_deployment
Related MCP Connectors
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Host apps in the EU from your assistant: App Store, Docker, GitHub, databases, logs.
Inspect and control your Northflank projects, services, jobs, and builds from your AI assistant.
Deploy and manage your apps, databases, storage, and scheduled jobs from your AI agent
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceDeploy, manage, and scale applications directly from your AI assistant.5-

Lizard MCPofficial
AlicenseAqualityAmaintenanceEnables deploying and managing apps on Lizard via natural language, covering services, deploys, logs, secrets, domains, and configuration as code.333MIT- AlicenseNot gradedqualityCmaintenanceEnables managing Sliplane deployments, projects, and application status through natural language, with OAuth or API key auth.MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage cloud infrastructure through natural language by providing a unified interface to the Dokploy platform. Supports Docker containers, applications, databases, domains, monitoring, and deployment operations through conversational commands.27 npm1-
Glama MCP Gateway
Add one secure layer between your agents and this server.