Let AI drive your DeployLane account.
A hosted MCP endpoint that gives Claude Code, Claude Desktop, Cursor and any other MCP‑capable client read or read/write access to the apps, servers and deploys attached to your DeployLane workspace. No SDKs to install, no glue to maintain.
01Quick start
Three steps from zero to chatting with your infra.
Generate a token
Open Settings → API access and click Generate token. Copy the value once — it’s shown only at creation.
Add DeployLane to your AI app
A few clicks in the Claude app, one command in Claude Code, or a short snippet in Cursor. Install walks you through it.
Ask in plain English
The model decides which tools to call. You describe what you want, not which API to hit.
02Install
Pick the AI app you use and follow its steps. You need two things: the address https://mcp.deploylane.dev and your token.
Have your token ready
Create one under Settings → API access in the dashboard. It starts with mcp_ and is shown only once, so keep it somewhere safe. Wherever the steps below say mcp_..., use your own token.
For the Claude desktop app and claude.ai in your browser. No files to edit.
- Open Claude and go to Customize → Connectors.
- Click + Add, then Add custom connector.
- Enter
DeployLaneas the name andhttps://mcp.deploylane.devas the URL, then continue. - For sign-in, choose No sign in.
- Under Request headers, add a header named
Authorizationwith the valueBearer mcp_...: the word Bearer, a space, then your token. - Click Add. Start a new chat and ask “Which apps do I have on DeployLane?”
Custom connectors need a paid Claude plan. On Team and Enterprise, an Owner adds the connector first.
03Authentication & scopes
Every request other than GET /health must carry a Bearer token. Each token has a scope you can change later from the dashboard — the plaintext stays the same so connected clients keep working.
Read‑only
List + inspect apps, servers, deploys, logs, metrics, backups and Umami analytics. Safe default — hand to any AI client you want to give visibility without trusting it to act on your account.
- list_*
- get_app, get_recent_deploys, get_deploy_log
- tail_logs, get_server_metrics, get_diagnose
- get_backup_history, get_pitr_status, get_umami_stats
Full access
Adds create / update / delete tools — provisioning new apps, setting env vars, managing cron jobs, deploying and rolling back, starting and stopping apps, rebooting and resizing servers. Only give to clients you trust to make changes.
- create_app, add_web_route, set_env_vars
- create_cron, update_cron, delete_cron
- trigger_deploy, rollback_app, start_app, stop_app
- reboot_server, resize_server, prune_docker, create_umami_website
Tokens are per‑user and scoped
Every tool query is scoped to the owning user’s data and cannot see other accounts. Revoke a leaked token from the dashboard — it’s effective immediately.
04Tools · 43
Everything the AI can call. Tool names are namespaced deploylane.<name> in clients (the prefix is muted below for readability).
deploylane.list_servers
deploylane.list_apps
deploylane.get_app
deploylane.get_recent_deploys
deploylane.get_deploy_log
deploylane.tail_logs
deploylane.get_server_metrics
deploylane.get_diagnose
deploylane.get_migration_guide
deploylane.get_umami_status
deploylane.get_umami_stats
deploylane.get_umami_timeseries
deploylane.get_umami_breakdown
deploylane.get_umami_top_pages
deploylane.get_umami_page_report
deploylane.compare_umami_periods
deploylane.create_app
deploylane.add_web_route
deploylane.set_env_vars
deploylane.create_cron
deploylane.trigger_deploy
deploylane.list_crons
deploylane.get_cron_history
deploylane.list_backup_jobs
deploylane.get_backup_history
deploylane.list_stored_backups
deploylane.get_pitr_status
deploylane.delete_env_var
deploylane.remove_web_route
deploylane.delete_cron
deploylane.update_cron
deploylane.restart_app
deploylane.start_app
deploylane.stop_app
deploylane.create_umami_website
deploylane.prune_docker
deploylane.get_disk_usage_report
deploylane.restart_traefik
deploylane.prune_orphaned_certs
deploylane.reboot_server
deploylane.resize_server
deploylane.get_resize_status
deploylane.rollback_app
05Prompts & resources
Server‑hosted prompt templates the AI invokes directly. In Claude Code: /mcp__deploylane__<name>. Clients that don’t surface prompts can invoke the equivalent tool instead.
Prompts
make_deploylane_ready
Make this repo DeployLane-ready
Walk the current repo through the DeployLane migration checklist: strip Vercel-specific bits, swap Neon/Vercel Blob for sibling Postgres + Hetzner S3, generate Dockerfile + docker-compose, finish with the env-vars + cron config the user needs to paste into the DeployLane UI.
Resources
deploylane://spec/v1
text/markdown
DeployLane app spec (v1) — Conventions a repo must follow to be deployable via DeployLane. Placeholder until the full spec lands.
06Example prompts
Real questions you can paste into your AI client. The model decides which tools to call and chains them together as needed — you stay in plain English.
07Rate limits
Per account, shared by all your tokens, in sliding 60‑second windows. Hitting a limit returns a clean tool error with a retry_after_seconds hint — not an HTTP 429 — so your AI client can back off without breaking the conversation.
Pure DB reads — list_apps, list_servers, get_app, get_recent_deploys, get_deploy_log, list_crons, list_backup_jobs, get_migration_guide.
Anything that SSHes into a server (tail_logs, get_server_metrics, get_diagnose), calls Umami or object storage, or mutates state. The cheap limit applies in addition.
Per‑app on trigger_deploy. Prevents parallel‑deploy storms from a runaway AI loop. Independent of deploy status.
Backoff hints, not HTTP 429
The MCP SDK has no concept of transport‑level retry semantics. AI clients DO read the error text — the rejected response includes a precise retry_after_seconds.