This project exposes LetsCloud's cloud platform through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io) so AI assistants like
Letscloud MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. This project exposes LetsCloud's cloud platform through the Model Context Protocol (MCP) so AI assistants like Claude, Cursor, Windsurf, VS Code Copilot, and any MCP-compatible client can.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Letscloud is connected, these are the calls the assistant has available:
get_account_info — GET /api/v1/accountlist_locations — GET /api/v1/locationslist_plans — GET /api/v1/locations/{slug}/planslist_images — GET /api/v1/locations/{slug}/imageslist_ssh_keys — GET /api/v1/ssh-keysget_ssh_key — GET /api/v1/ssh-keys/{title}create_ssh_key — POST /api/v1/ssh-keysdelete_ssh_key — DELETE /api/v1/ssh-keys/{slug}list_servers — GET /api/v1/instancesget_server — GET /api/v1/instances/{id}create_server — POST /api/v1/instancesdelete_server — DELETE /api/v1/instances/{id}You will need one environment variable: YOUR_LETSCLOUD_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Letscloud's toolset — get_account_info, list_locations, list_plans and 11 more — is a fair guide to whether it matches your workflow. It is maintained by letscloud-community; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_account_info | GET /api/v1/account |
| list_locations | GET /api/v1/locations |
| list_plans | GET /api/v1/locations/{slug}/plans |
| list_images | GET /api/v1/locations/{slug}/images |
| list_ssh_keys | GET /api/v1/ssh-keys |
| get_ssh_key | GET /api/v1/ssh-keys/{title} |
| create_ssh_key | POST /api/v1/ssh-keys |
| delete_ssh_key | DELETE /api/v1/ssh-keys/{slug} |
| list_servers | GET /api/v1/instances |
| get_server | GET /api/v1/instances/{id} |
| create_server | POST /api/v1/instances |
| delete_server | DELETE /api/v1/instances/{id} |
| start_server | PUT /api/v1/instances/{id}/power-on |
| shutdown_server | PUT /api/v1/instances/{id}/power-off |
{
"mcpServers": {
"letscloud": {
"url": "https://mcp.letscloud.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_LETSCLOUD_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| YOUR_LETSCLOUD_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.