get_deploy_instructionsLABSCO SUMMARY
Separate delete scope and a QA-run tool are what make handing this to an agent reasonable.
Deployment tools are where agent mistakes get expensive, and two things here help. The scopes split read from write from delete, so a client can be given exactly as much as its job needs. And get_e2e_qa_run_details means a deploy that failed can be explained by the agent instead of sending you to a dashboard. The source-reading tools are the surprise: most deploy servers assume the code is someone else's problem.
What it is
AppDeploy's endpoint. Alongside the deploy tools it exposes three for reading source — glob, grep and read — so the agent can find what it is about to ship rather than being told.
What you get
- Deploy instructions, app templates and an SDK reference the agent can read before it builds
- Source navigation: src_glob, src_grep, src_read
- Deploy an app, upload assets, apply a version, and read app status and version history
- End-to-end QA run details, so a failed deploy comes with the test output
- Custom domain configuration, and app deletion
Requirements
OAuth 2.1 with three scopes — deploy:read, deploy:write and deploy:delete — so read-only access is grantable on its own. Free tier covers build, deploy, hosted URL, database, storage, auth, cron and rollback under fair use.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Shipping a change end to end
Read the deploy instructions, push the version, then check status and the QA run rather than assuming it worked.
02
Finding the code that needs changing
Glob for the files, grep for the symbol, read only what matched — instead of loading a repo into context.
03
Rolling back to a known-good version
List the app's versions and apply the one that worked.
04
Granting an agent read-only deploy access
Issue a token with deploy:read alone, so it can report on deployments without making one.
16 tools
Listed in project docs. Your client may show a different list.
get_app_templateget_appdeploy_sdk_referenceget_app_statusget_e2e_qa_run_detailsget_app_versionssrc_globsrc_grepsrc_readget_appsget_custom_domain_instructionsdeploy_appupload_assetsapply_app_versiondelete_appconfigure_custom_domainBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.1 Bearer
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://api-v2.appdeploy.ai/mcpRequirements
- OAuth 2.1 Bearer
