Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DEPLOYADO_BASE_URLNoAPI base URLhttps://deployado.com
DEPLOYADO_API_TOKENYesAPI token from Settings → API Tokens (https://deployado.com/settings/api-tokens). This is separate from the CLI's `deployado auth login`.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
deployado_whoamiA

Show current account, user, and API token information. Useful to verify authentication is working.

deployado_list_appsB

List all apps in your Deployado account. Optionally filter by project ID.

deployado_get_appC

Get detailed information about a specific app.

deployado_create_appA

Create a new app in a project.

IMPORTANT: Apps with a repository_url are built using Docker. The repository MUST contain a Dockerfile (at dockerfile_path, default "Dockerfile" relative to build_context).

For static websites (HTML/CSS/JS), add a simple Dockerfile: FROM nginx:alpine COPY . /usr/share/nginx/html EXPOSE 80

Key parameters:

  • repository_url: Git repo URL (HTTPS). Required for repo-based apps.

  • dockerfile_path: Path to Dockerfile relative to build_context (default: "Dockerfile").

  • build_context: Subdirectory where Docker build runs, relative to repo root (default: "."). Use this when your site is in a subfolder (e.g. "website").

  • port: The port your app listens on inside the container. For nginx use 80, for Node.js typically 3000 or 8080.

  • branch: Git branch to build from (default: "main").

deployado_update_appC

Update an existing app's configuration.

deployado_delete_appA

Permanently delete an app and all its deployments, releases, and environment variables. Its running containers are stopped and removed on the app server (queued agent action). Fails with 409 deploy_in_progress while a deploy is executing; retry once it finishes. This action cannot be undone.

deployado_deployA

Trigger a new deployment for an app. Returns immediately with a release_id while the build runs in the background.

The deployment process: source code is cloned → Docker image is built → image is pushed → container is deployed.

After triggering:

  • Use deployado_get_release with the returned release_id to check build status (queued → pending → building → ready or failed).

  • If the build fails, use deployado_get_build_logs with the release_id to see the Docker build output.

  • commit_sha is optional — if omitted, the latest commit from the configured branch is used.

  • For runtime container logs after deployment, use deployado_get_logs.

deployado_rollbackC

Rollback an app to a previous release version.

deployado_list_releasesA

List available releases for an app, showing version history and build status. Each release has a status: queued, pending, building, ready (success), or failed. Use deployado_get_build_logs with a release_id to see build output.

deployado_get_logsA

Fetch recent runtime logs from a running app's container. NOTE: These are runtime/application logs, NOT build logs. To see build output (e.g. why a deploy failed), use deployado_get_build_logs instead.

deployado_get_releaseA

Get detailed information about a specific release, including build status, commit info, and error details. Use this to check if a build succeeded or failed after triggering a deploy.

deployado_get_build_logsA

Fetch build logs for a specific release. Use this to diagnose why a build failed.

Returns the Docker build output, including Dockerfile parsing errors, dependency installation logs, and compilation output. If the build is still in progress, returns partial logs collected so far.

IMPORTANT: This returns BUILD logs (from the Docker build process), not runtime container logs. For runtime logs of a running app, use deployado_get_logs instead.

deployado_list_deploymentsA

List recent deployments for an app, showing status, version, and timing.

deployado_get_deploymentB

Get detailed information about a specific deployment, including phases and error details.

deployado_current_deploymentA

Get the currently active deployment for an app.

deployado_list_envA

List all environment variables for an app. Values of secret variables may be masked.

deployado_set_envA

Set or update environment variables for an app. Merges with existing variables. A redeploy may be triggered automatically.

deployado_delete_envC

Delete a single environment variable from an app.

deployado_list_serversA

List all servers with their status and resource metrics (CPU, memory, disk).

deployado_get_serverA

Get detailed information about a specific server, including agent version, OS, architecture, and Docker version.

deployado_list_projectsB

List all projects in your Deployado account.

deployado_get_projectA

Get detailed information about a specific project.

deployado_create_projectC

Create a new project in your Deployado account.

deployado_update_projectC

Update a project's name, description, or other settings.

deployado_delete_projectA

Delete a project and all its associated apps, stopping and removing each app's containers. Fails with 409 deploy_in_progress while one of its apps is being deployed. This action cannot be undone.

deployado_list_databasesA

List all managed PostgreSQL databases. Optionally filter by project or status.

deployado_get_databaseA

Get detailed information about a database, including connection URL and credentials.

deployado_create_databaseA

Create a new managed PostgreSQL database. The database name will be auto-prefixed with your account slug.

deployado_delete_databaseA

Permanently delete a managed PostgreSQL database. This will drop the database and remove all data. This action cannot be undone.

deployado_connect_databaseA

Connect an app to a database. This injects the connection URL as an environment variable into the app.

deployado_disconnect_databaseB

Disconnect an app from a database, removing the injected environment variable.

deployado_execA

Execute a command inside an app's running container. Timeout is 60 seconds. Returns exit code, stdout, and stderr.

deployado_validate_blueprintA

Validate a Deployado blueprint YAML without deploying it. Returns validation results and a preview of what would be created.

deployado_deploy_blueprintB

Deploy an entire application stack from a blueprint. Can use inline YAML content or a GitHub repository URL.

deployado_list_domainsB

List all custom domains for an app, including the auto-generated subdomain.

deployado_add_domainA

Add a custom domain to an app. You must configure DNS (CNAME or A record) separately.

deployado_remove_domainC

Remove a custom domain from an app.

deployado_set_primary_domainB

Set a domain as the primary domain for an app. The primary domain is used for redirects.

deployado_verify_domainsA

Verify DNS configuration for all domains of an app. Returns per-domain verification status.

deployado_list_cron_jobsA

List all cron jobs for an app.

deployado_create_cron_jobC

Create a new cron job for an app.

deployado_update_cron_jobC

Update an existing cron job.

deployado_delete_cron_jobC

Delete a cron job.

deployado_run_cron_jobB

Manually trigger a cron job to run immediately.

deployado_list_service_templatesB

Browse available service templates from the Deployado marketplace (databases, caches, monitoring tools, etc.).

deployado_list_servicesB

List all installed services for your account.

deployado_get_serviceC

Get detailed information about a specific installed service.

deployado_install_serviceC

Install a new service from a marketplace template.

deployado_start_serviceA

Start a stopped service.

deployado_stop_serviceC

Stop a running service.

deployado_restart_serviceC

Restart a service.

deployado_list_backup_targetsA

List all database backup targets configured for your account.

deployado_create_backup_targetB

Create a new database backup target. Backups are stored in S3.

deployado_get_backup_targetB

Get a backup target's details and its recent backup runs.

deployado_run_backupC

Trigger an immediate backup for a target.

deployado_restore_backupA

Restore a database from a specific backup run. This will overwrite the target database.

deployado_doctorA

Run a fixed diagnostic checklist against one app. Returns structured results plus a roll-up: deployment status, latest build, target server health, instance count, HTTP probe of the primary domain, env vars, placement. Use this as the first stop when triaging 'app X is acting weird'. Mirrors the deployado doctor CLI command.

deployado_release_logsA

Fetch the docker build transcript for a release. Works for both in-progress and finished builds. Returns the full logs plus status/timing metadata. Use this when investigating a build failure — the release ID comes from deployado deploy output or the releases field of an app's deployment.

Prompts

Interactive templates invoked by user choice

NameDescription
deployado_statusGet a full overview of your Deployado infrastructure — apps, servers, and databases.

Resources

Contextual data attached and managed by the client

NameDescription
apps-listSummary of all apps in the Deployado account with their IDs, names, and projects.
servers-listOverview of all servers with their status and resource metrics.

TDQS

B3.2/5.0

Scored across 58 tools

Disambiguation4/5

Most tools target distinct resources and actions, and descriptions clarify the deployment/release/doctor triage cluster. The main weak spot is the near-duplicate pair deployado_get_build_logs and deployado_release_logs, which both fetch the Docker build transcript for a release, forcing an arbitrary choice.

Naming Consistency5/5

Every tool uses the deployado_ prefix with a consistent snake_case verb_noun pattern (get_app, create_project, list_databases, run_backup). Even the singular nouns and the one-verb deploy_blueprint fit the pattern predictably.

Tool Count2/5

58 tools is far beyond a well-scoped set and includes redundant log fetchers. The domain (apps, projects, deployments, databases, services, domains, cron, backups) justifies a large surface but not this many; it is heavy enough to burden selection.

Completeness4/5

Lifecycle coverage is strong: CRUD for apps, projects, databases, cron jobs, env vars, plus deploy/rollback, exec, logs, backups, and diagnostics. Minor gaps remain, e.g. no domain update (only add/remove/set-primary) and no database resize/rename operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues