AppDeploy MCP Server for Claude
AppDeploy hosted MCP server for chat-native full-stack web app deployment with templates, QA snapshots, version rollback, and live public URLs from Claude or ChatGPT.
Open the source and read safety notes before installing.
Safety notes
- deploy_app publishes publicly reachable URLs; review app content before deploying.
- delete_app permanently removes apps—use only on explicit user request.
- Deployed apps may access AppDeploy-provided database, storage, and auth services.
- OAuth sessions grant persistent deploy access until disconnected.
Privacy notes
- App source, deployment logs, and QA snapshots are stored on AppDeploy infrastructure.
- Public URLs may expose app functionality and any data users submit to the deployed app.
- Guest OAuth still ties deployments to an AppDeploy identity—avoid sharing accounts.
Prerequisites
- AppDeploy account via OAuth (Google, Apple, X, or Guest).
- Claude Pro/Team with Connectors, ChatGPT, Cursor, Codex, or Grok MCP support.
- Clear description of the app you want deployed before invoking write tools.
- Awareness that deploy_app and delete_app are destructive operations.
Schema details
- Install type
- cli
- Reading time
- 4 min
- Difficulty score
- 30
- Troubleshooting
- Yes
- Breaking changes
- No
- Estimated setup
- 5 minutes
- Difficulty
- beginner
- Website
- https://appdeploy.ai
Full copyable content
{
"mcpServers": {
"appdeploy": {
"url": "https://api-v2.appdeploy.ai/mcp",
"type": "http"
}
}
}About this resource
Overview
AppDeploy is a chat-native deployment platform exposed through Model Context Protocol. Describe an app in Claude, ChatGPT, Cursor, or Codex and AppDeploy returns a live public URL with hosting, optional backend services, autonomous black-box QA, and version rollback—no Git or manual infra setup required.
Documentation: appdeploy.ai/mcp-docs. Endpoint: https://api-v2.appdeploy.ai/mcp.
Features
- Deploy frontend-only and full-stack apps with public URLs.
- get_app_template and get_deploy_instructions for agent-guided builds.
- Autonomous E2E QA with snapshots and runtime error reporting.
- Version listing and apply_app_version rollback.
- OAuth authentication with multiple identity providers.
Use Cases
- Deploy a Pomodoro timer or team leaderboard from a single chat prompt.
- Iterate on a bakery pre-order site and inspect QA failures.
- Roll back a broken deployment to the previous version.
- Upload binary assets before deploying a media-heavy app.
- List all apps owned by the current user before updating one.
Installation
Claude (Connectors)
- Open Claude Settings → Connectors → Add custom connector.
- Name it AppDeploy and set URL to
https://api-v2.appdeploy.ai/mcp. - Complete OAuth sign-in when prompted.
- Ask the assistant to fetch deploy instructions before the first deploy_app call.
Claude Code
claude mcp add --transport http appdeploy https://api-v2.appdeploy.ai/mcp
claude mcp list
Other MCP clients
Add the connector using the JSON configuration below in your MCP client settings.
Configuration
{
"mcpServers": {
"appdeploy": {
"url": "https://api-v2.appdeploy.ai/mcp",
"type": "http"
}
}
}
OAuth handles authentication; no manual API key is required for standard connector setup.
Examples
New app
Deploy a Pomodoro timer with start, pause, reset, and a notification sound when time is up.
Check status
Call get_app_status for my latest app and summarise QA results.
Rollback
Roll back my bakery app to the previous working version.
Security
- Review generated code and third-party dependencies before deploying public apps.
- Do not deploy apps that collect sensitive data without proper auth and encryption.
- Use delete_app only after explicit user confirmation.
Troubleshooting
Tools fail after connect
Disconnect and reconnect to refresh the OAuth token.
Deployment stuck deploying
Wait one to two minutes and poll get_app_status again.
Blank live page
Inspect runtime errors via get_app_status and redeploy fixes.
QA failures
Call get_e2e_qa_run_details, fix code, and redeploy.
Duplicate Check
No existing AppDeploy or api-v2.appdeploy.ai entry was found in content/mcp/. This differs from Vercel or Netlify MCP integrations because AppDeploy is chat-native with built-in QA and templated full-stack deploy flows.
Source citations
Add this badge to your README
How it compares
AppDeploy MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | AppDeploy MCP Server for Claude AppDeploy hosted MCP server for chat-native full-stack web app deployment with templates, QA snapshots, version rollback, and live public URLs from Claude or ChatGPT. Open dossier | Alpic MCP Server for Claude Alpic hosted MCP server to manage cloud-hosted MCP projects—deployments, debugging, and analytics—for apps built and shipped on the Alpic platform. Open dossier | Agent Device MCP Server Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps. Open dossier | AutoRFP.ai MCP Server for Claude Official AutoRFP.ai remote MCP server for read-only access to RFP projects, requirements, approved content library search, and organisation tags from Claude and other MCP clients via OAuth. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | AppDeploy | Alpic | Callstack | AutoRFP.ai |
| Added | 2026-06-14 | 2026-06-14 | 2026-06-06 | 2026-06-14 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓deploy_app publishes publicly reachable URLs; review app content before deploying. delete_app permanently removes apps—use only on explicit user request. Deployed apps may access AppDeploy-provided database, storage, and auth services. OAuth sessions grant persistent deploy access until disconnected. | ✓Management tools may trigger redeployments or configuration changes on hosted MCP servers. Analytics and logs may contain end-user queries from your deployed MCP apps. Do not share Alpic credentials across untrusted chat sessions. Verify target project/environment before approving destructive deploy actions. | ✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP. Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions. Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files. Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work. Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts. | ✓The connection is read-only; it cannot create, edit, or delete AutoRFP.ai records. Each user inherits their own AutoRFP.ai permissions, so MCP results reflect that user's normal app access. OAuth tokens grant persistent read access until revoked in AutoRFP.ai or the MCP client. Do not share OAuth-approved connector sessions across users or paste access tokens into public issues. |
| Privacy notes | ✓App source, deployment logs, and QA snapshots are stored on AppDeploy infrastructure. Public URLs may expose app functionality and any data users submit to the deployed app. Guest OAuth still ties deployments to an AppDeploy identity—avoid sharing accounts. | ✓Project metadata, deployment logs, and analytics are processed by Alpic. End-user traffic to your deployed MCP apps is subject to Alpic platform terms. Store Alpic auth tokens in connector secrets, not in repositories. | ✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials. macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts. Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing. Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set. | ✓MCP tool results can expose RFP project names, requirement text, approved answer content, and organisation tag vocabulary. Search queries sent to the content library are processed by AutoRFP.ai under its own data-handling terms. Public support notes should describe connector scope, not full requirement or library excerpts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.