canonical: https://jentic.com/apis/appdeploy.ai/appdeploy # AppDeploy MCP API The AppDeploy API deploys and manages web applications through a single JSON-RPC endpoint, with OAuth scopes that separate reading deployment state from writing versions and removing apps. Read operations list and inspect apps, deployment status, versions, logs, and source; write operations create or update deployments, apply versions, and change app configuration; a separate delete scope covers removing an app. Two discovery endpoints publish the OAuth protected-resource and authorization-server metadata so clients can complete the auth flow. ## For AI agents Deploy and manage web applications: create and update deployments, apply versions, read status and logs, change configuration, and delete apps under scoped permissions. ## Scope Does not host databases, manage DNS, or run CI build pipelines. Use for deploying and managing web applications only. ## Capabilities - Create and update web application deployments - Apply a specific version to a deployed app - List and inspect apps, deployment status, versions, logs, and source - Change an app's configuration - Delete an app under an explicit destructive scope ## Use cases ### AI agent deploying an app A coding agent that has just built a change needs to ship it without a developer running deploy commands. Through Jentic the agent searches for deploying a new app version, loads the deployment operation with its OAuth credentials already injected, and submits the deployment request. The agent gets back the deployment result so it can confirm the ship succeeded. Example prompt: Call POST /mcp with a request to create a deployment for the app and confirm the returned status ### Deployment status checks An agent monitoring a release reads deployment status, versions, and logs to decide whether a rollout is healthy. AppDeploy's read scope lists and inspects apps, deployment status, versions, logs, and source, so the agent can report on a release without write access. This supports a read-only monitoring role separate from the agent that ships changes. Example prompt: Call POST /mcp with a request to read the current deployment status and recent logs for an app ### Configuration updates An operations agent needs to change an app's configuration and apply it as part of a deployment. AppDeploy's write scope covers creating or updating deployments, applying versions, and changing configuration, so the agent can adjust settings and roll them out in the same flow. The delete scope stays separate so configuration work never risks removing the app. Example prompt: Call POST /mcp with a request to update the app configuration and apply the new version ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/mcp` | Send a JSON-RPC deployment message | | GET | `/.well-known/oauth-protected-resource/mcp` | Get the protected-resource metadata | | GET | `/.well-known/oauth-authorization-server` | Get the authorization-server metadata | ## Key resources - **Deployments** — Create and update deployments, apply versions, and change configuration through the JSON-RPC endpoint - **App state** — List and inspect apps, deployment status, versions, logs, and source - **Discovery** — OAuth protected-resource and authorization-server metadata endpoints ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 64 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 67 / 100 - **View full report:** https://jentic.com/apis/appdeploy.ai/appdeploy/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the AppDeploy API by hand means completing its OAuth 2.0 authorization code flow with PKCE and dynamic client registration, or falling back to a bearer token, and routing every tool call through its single JSON-RPC endpoint. Through Jentic you install once, import AppDeploy from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** AppDeploy declares separate OAuth scopes for reading deployment state, writing deployments, and deleting apps. You choose the operations your agent may call, so you can allow the read and write operations and leave the destructive delete out of the allowed set unless you add it. - **Credential handling:** Your AppDeploy credentials are stored once, encrypted, by your own Jentic One instance, which completes the OAuth exchange at execution time. They never enter the agent's prompt, logs, or context, nor does the resulting access token. - **Discovery method:** Agents search Jentic by intent such as 'deploy a new app version' or 'check deployment status', and Jentic returns the matching AppDeploy operation with its input schema so the agent calls the right one without reading the reference docs. ## Related APIs - **Render API** — Deploys and manages apps and services on the Render platform - **Cloud 66 API** — Builds and deploys applications across your own cloud infrastructure - **DigitalOcean API** — Provisions the underlying droplets, databases, and networking an app runs on ## FAQ ### What authentication does the AppDeploy API use? The AppDeploy API uses OAuth 2.0 with the authorization code flow, PKCE, and dynamic client registration, declaring separate scopes for reading, writing, and deleting, per its OpenAPI spec. Clients that cannot complete OAuth may send a bearer access token or API key instead, though OAuth is preferred because it carries scopes. The two discovery endpoints need no credential. Through Jentic the OAuth exchange runs at call time, so the agent receives only a scoped token. ### Can I deploy a new app version with the AppDeploy API? Yes. With the write scope, an agent sends a deployment request to POST /mcp to create or update a deployment and apply a version. The read scope then lets it confirm the deployment status and inspect logs without any further write access. ### What are the rate limits for the AppDeploy API? The OpenAPI spec does not define request-rate ceilings. Throughput is governed by your AppDeploy plan and the scopes your token holds. Check the AppDeploy documentation for the limits that apply to your account before scripting frequent deployments. ### Is there an AppDeploy MCP server? AppDeploy exposes its tools through a JSON-RPC endpoint, and Jentic connects that endpoint directly from the API Directory using its OpenAPI spec. Import the API, store your OAuth credentials once, and your agent calls the deployment operations on demand, with no separate server to run or keep loaded in the agent's context. ### Can I limit what my agent is allowed to do with the AppDeploy API? Yes. Write a rule that allows only the read and write scopes, so the agent can inspect deployments and ship new versions but cannot invoke the destructive delete scope that removes an app, and every call it makes is logged. You add the delete scope to the allowed set only when you explicitly want it. ### How do I deploy an app through Jentic? Search Jentic for 'deploy a new app version', load the deployment operation, and run it after your OAuth credentials are stored. To run it on your own infrastructure, install Jentic One from its GitHub repo.