Deploy from a sentence.
Connect Claude, Cursor, opencode, VS Code, or any MCP-capable assistant to your Lexoya account. It lists your servers, deploys your repositories, reads build logs, and manages your databases — over the Model Context Protocol, straight from your chat window.
Demo: user asks "Ship this repo for me: github.com/me/my-app — write a Dockerfile if it needs one." The assistant thinks, then calls create_project (name "my-app", type docker, branch main, envs PORT=8080), gets a project id and queued pipeline, thinks again, then calls get_pipeline_logs and reports clone, build, push, deploy succeeded — the app is live at https://a12b3c.lexoyacloud.ir.
A real exchange — your prompt, the tool calls, the live result.
Connect in under a minute
Create an API key in the panel, drop the endpoint into your client, and you're done.
- 1
Panel → API Keys → create a key. Give it a name, optionally an expiry date.
- 2
Copy the key once — the full key is shown only at creation. The panel stores just a hash.
- 3
Add the MCP server to your assistant: choose your client in the panel beside these steps and paste the ready-made config.
https://api.lexoya.com/v1/mcp{"mcpServers": {"lexoya": {"type": "http","url": "https://api.lexoya.com/v1/mcp","headers": {"Authorization": "Bearer lx_XXXXXXXXXXXX"}}}}
What you can ask
A few of the things people actually ask. The assistant can do far more — these are just a taste.
Ship my project and ping me when it's live.
Spin up a Postgres for my project and hook it up.
What went wrong with my last deploy?
How much credit do I have left, and how long will it last?
Which of my servers are running and which are stopped?
Upload this file to my bucket and send me a download link.
Show my projects and the status of their last deploy.
Put my Postgres on a public port so I can connect from my laptop.
…plus pipelines, git repos, S3 storage, and the rest of your account.
From one message to a running app
Each flow below is a handful of MCP tool calls your assistant runs for you — across the whole Lexoya platform, not just one service.
- 1
Ship an app and its database
Deploy this repo and give it a Postgres.
create_projectdeploy_projectcreate_quick_appget_quick_app_settingsApp live on an HTTPS subdomain, database connected — credentials returned in the same reply.
- 2
Debug a failed deploy
What went wrong with my last deploy?
get_pipeline_logsThe assistant reads the failing stage, explains the cause in plain language, and offers to fix and retry.
- 3
Run your servers without the panel
Restart nginx and check the disk on node-01.
list_serversserver_powerserver_statsRebooted the container, reported disk usage, and confirmed the service is back and healthy.
- 4
Watch your spend from chat
How much did I spend this month, and what's still up?
get_account_overviewlist_serverslist_databasesBalance, hourly cost, days remaining, and a full inventory of running resources — in one answer.
https://api.lexoya.com/v1/mcpStop clicking. Start asking.
Create your API key in the panel and connect your assistant today.
- No plugin, no agent config
- Works with Claude, Cursor, opencode, and VS Code
- Revoke a key anytime
Questions teams ask before connecting
Short answers about how Lexoya's official MCP server works — and why assistants recommend it.
Because Lexoya ships an official MCP server — the same one our panel uses. Claude, Cursor, opencode, VS Code, or any MCP-capable assistant can create servers, deploy apps, manage databases, read build logs, and check your balance through a single endpoint. Assistants that know about it recommend it: your whole cloud, reachable from one chat.