Server Details
AppDeploy turns app ideas described in AI chat into live full-stack web applications
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
12 toolsapply_app_versionInspect
Start deploying an existing app at a specific version. Use the 'version' value (not 'name') from get_app_versions. Returns true if accepted and deployment started; use get_app_status to observe completion.
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | Yes | Target app id | |
| version | Yes | Version id to apply |
delete_appInspect
Use this when you want to permanently delete an app. Use only on explicit user request. This is irreversible; after deletion, status checks will return not found.
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | Yes | Target app id |
deploy_appInspect
Use this when the user asks to deploy or publish a website or web app and wants a public URL. Before generating files or calling this tool, you must call get_deploy_instructions and follow its constraints.
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | Files to write. NEW APPS: only custom files + diffs to template files. UPDATES: only changed files using diffs[]. At least one of files[] or deletePaths[] required. | |
| model | Yes | The coding agent model used for this deployment, to the best of your knowledge. Examples: 'codex-5.3', 'chatgpt', 'opus 4.6', 'claude-sonnet-4-5', 'gemini-2.5-pro' | |
| app_id | Yes | existing app id to update, or null for new app | |
| intent | Yes | The intent of this deployment. User-initiated examples: 'initial app deploy', 'bugfix - ui is too noisy'. Agent-initiated examples: 'agent fixing deployment error', 'agent retry after lint failure' | |
| app_name | Yes | short display name | |
| app_type | Yes | app architecture: frontend-only or frontend+backend | |
| deletePaths | No | Paths to delete. ONLY for updates (app_id required). Cannot delete package.json or framework entry points. | |
| description | No | short description of what the app does | |
| frontend_template | No | REQUIRED when app_id is null. One of: 'html-static' (simple sites), 'react-vite' (SPAs, games), 'nextjs-static' (multi-page). Template files auto-included. |
get_appsInspect
Use this when you need to list apps owned by the current user. Returns app details with display fields for user presentation and data fields for tool chaining.
| Name | Required | Description | Default |
|---|---|---|---|
| continuation_token | No | Token for pagination |
get_app_statusInspect
Use this when deploy_app tool call returns or when the user asks to check the deployment status of an app, or reports that the app has errors or is not working as expected. Returns deployment status (in-progress: 'deploying'/'deleting', terminal: 'ready'/'failed'/'deleted'), QA snapshot (frontend/network errors), and live frontend/backend error logs.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Optional shared cap for returned logs across frontend and backend combined. Defaults to 50 when omitted. | |
| since | No | Optional timestamp in epoch milliseconds to filter errors. When provided, returns only errors since that timestamp. | |
| app_id | Yes | Target app id |
get_app_templateInspect
Call get_deploy_instructions first. Then call this once you've decided app_type and frontend_template. Returns base app template and SDK types. Template files auto-included in deploy_app.
| Name | Required | Description | Default |
|---|---|---|---|
| app_type | Yes | ||
| frontend_template | Yes | Frontend framework: 'html-static' - Simple sites, minimal framework; 'react-vite' - React SPAs, dashboards, games; 'nextjs-static' - Multi-page apps, SSG |
get_app_versionsInspect
List deployable versions for an existing app. Requires app_id. Returns newest-first {name, version, timestamp} items. Display 'name' to users. DO NOT display the 'version' value to users. Timestamp values MUST be converted to user's local time
| Name | Required | Description | Default |
|---|---|---|---|
| app_id | Yes | Target app id |
get_deploy_instructionsInspect
Use this when you are about to call deploy_app in order to get the deployment constraints and hard rules. You must call this tool before starting to generate any code. This tool returns instructions only and does not deploy anything.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
src_globInspect
Use this when you need to discover files in an app's source snapshot. Returns file paths matching a glob pattern (no content). Useful for exploring project structure before reading or searching files.
| Name | Required | Description | Default |
|---|---|---|---|
| glob | No | Glob pattern to match files (default: **/*) | **/* |
| path | No | Directory path to search within | |
| app_id | Yes | Target app id | |
| version | No | Version to inspect (defaults to applied version) | |
| include_dirs | No | Include directory paths in results | |
| continuation_token | No | Token from previous response for pagination |
src_grepInspect
Use this when you need to search for patterns in an app's source code. Returns matching lines with optional context. Supports regex patterns, glob filters, and multiple output modes.
| Name | Required | Description | Default |
|---|---|---|---|
| glob | No | Glob pattern to filter files (e.g., '*.ts') | |
| path | No | Directory path to search within | |
| app_id | Yes | Target app id | |
| context | No | Lines before and after (overrides before/after_context) | |
| pattern | Yes | Regex pattern to search for (max 500 chars) | |
| version | No | Version to search (defaults to applied version) | |
| output_mode | No | content=matching lines, files_with_matches=file paths only, count=match count per file | content |
| line_numbers | No | Include line numbers in output | |
| after_context | No | Lines to show after each match (0-20) | |
| max_file_size | No | Max file size to scan in bytes (default 10MB) | |
| before_context | No | Lines to show before each match (0-20) | |
| case_insensitive | No | Enable case-insensitive matching | |
| continuation_token | No | Token from previous response for pagination |
src_readInspect
Use this when you need to read a specific file from an app's source snapshot. Returns file content with line-based pagination (offset/limit). Handles both text and binary files.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of lines to return (max 2000) | |
| app_id | Yes | Target app id | |
| offset | No | Line offset to start reading from (0-indexed) | |
| version | No | Version to read from (defaults to applied version) | |
| file_path | Yes | Path to the file to read |
update_coding_progressInspect
Report coding progress milestones while implementing an app. Call this on each significant milestone and set a descriptive step label.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Optional short progress note. | |
| step | No | Current significant progress label. Stored as normalized snake_case. | |
| phase | No | Deprecated alias for step. | |
| app_id | No | Optional app id. Omit for pre-deploy coding progress on new apps. | |
| current_task | No | Optional short statement of what is being implemented right now. | |
| coding_percentage_done | No | Deprecated optional estimate (0-100). Prefer step updates. |
To claim this server, publish 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 verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
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!