Scoped permissions
The agent only gets what your Devopness role allows. No full cloud admin keys in editor config.
Model Context Protocol (MCP)
Deploy from your IDE
Install Devopness MCP in your editor. Deploy apps and manage servers in your cloud from a prompt. OAuth sign-in. API keys stay out of chat.
How it works
Your prompt hits Devopness MCP. The change runs in your cloud. Keys stay out of chat.
OAuth sign-in
Remote HTTP MCP with OAuth. No tokens in mcp.json, chat logs, or screenshots.
Logged in Devopness
Every MCP action records who ran it and what changed.
Installation
Cursor and VS Code: one-click install. Other tools link to a step-by-step guide in docs.
AI tools
Example prompts
Paste these into your editor once MCP is connected.
Deployments
- "Deploy 'my-app' to staging"
- "Deploy my-app cool-feature branch"
- "Rollback 'my-app' to previous version"
- "Show 'my-app' deployment history"
Servers
- "List DEV servers"
- "API dev server details + metrics"
- "Restart API dev web server"
- "Check server health"
Environments
- "Create staging env"
- "List env variables"
- "Set DATABASE_URL for app 'my-app'"
- "Clone prod 'my-app' to 'staging-my-app'"
Applications
- "List apps"
- "Show 'my-app' config"
- "Update 'my-app' .env file"
- "'Github my/repo' apps status in all envs"