aptible-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listAccountsA | List all accounts/environments. |
| getAccountB | Get account/environment by handle. |
| getAccountsByStackA | Get all accounts/environments in a stack by stack name. |
| createAccountC | Create a new account/environment. |
| listAppsA | List all apps. |
| getAppA | Get app by handle. Because app names are only unique within an account/environment, an account handle can also be provided. |
| createAppC | Create a new app. |
| configureAppC | Configure app environment variables. |
| deleteAppC | Delete an app. |
| listAvailableDatabaseTypesA | List all available database types. When creating a database, the image id provided via this method is needed. |
| listDatabasesA | List all databases. |
| getDatabaseA | Get database by handle and optionally account handle. |
| createDatabaseA | Create a new database. The image_id should be the ID found via listAvailableDatabaseTypes. |
| deleteDatabaseC | Delete a database. |
| listStacksB | List all stacks. |
| getStackC | Get stack by name. |
| listVhostsB | List all vhosts/endpoints). |
| getVhostB | Get vhost by ID. |
| createVhostA | Create a new vhost/endpoint for a Service. Service handle is a bit weird, since it's auto-assigned by Aptible and not set by the user. The user assigns with process_type in the procfile. Since this is being used by AI, that shouldn't matter, though. TODO: Add support for database endpoints and custom endpoints. Currently, since there's no tools for handling DNS, we only support creating the default on-aptible.com domains for Services. |
| deleteVhostB | Delete a vhost/endpoint. |
| listServicesA | List all services for a specific app. |
| getServiceB | Get a service by handle within a specific app. |
| scaleServiceB | Scale a service by changing container count or size. |
| listServiceVhostsB | List all vhosts for a specific service. |
| getOperationsForAppC | Get recent operations for a specific app. |
| getOperationsForDatabaseB | Get recent operations for a specific database. |
| getOperationsForVhostB | Get recent operations for a specific vhost/endpoint. |
| getOperationLogsB | Get logs for a specific operation. |
| getProcfileExampleA | Gets an example Procfile for defining app processes. Keep in mind that 1-off tasks like running migrations are better suited for processes run via .aptible.yml, and do not belong in the Procfile. The finalized Procfile file should be located in /.aptible/Procfile in the build Docker image. |
| getAptibleYamlExampleA | Gets an example aptible.yml configuration file for deploy hooks. The finalized .aptible.yml file should be located in /.aptible/.aptible.yml in the build Docker image. |
| getEndpointProvisionExampleA | Gets an example of a GitHub Action for provisioning an endpoint. |
| getAppProvisionExampleA | Gets an example of a GitHub Action for provisioning an app. |
| getAppDeprovisionExampleA | Gets an example of a GitHub Action for deprovisioning an app. |
| getAppConfigureExampleA | Gets an example of a GitHub Action for configuring an app. |
| getDatabaseProvisionExampleA | Gets an example of a GitHub Action for provisioning a database. |
| getDatabaseDeprovisionExampleA | Gets an example of a GitHub Action for deprovisioning a database. |
| getDatabaseRestoreExampleA | Gets an example of a GitHub Action for restoring a database from backup. |
| getBuildDeployExampleA | Gets an example of a GitHub Action for building, publishing, and deploying an app. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aptible/aptible-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server