scalingo
Server Details
Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
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. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!