Cloud infrastructure automation is entering a new phase. Instead of relying only on dashboards, scripts, or manual API calls, it is now possible to interact with cloud resources using natural language.
That is exactly the purpose of the LetsCloud MCP Server: to connect AI assistants, such as Claude, to LetsCloud infrastructure through the Model Context Protocol, also known as MCP.
With this integration, Claude can help with tasks such as checking cloud instances, listing available images, verifying locations, reviewing snapshots, managing SSH keys, and supporting infrastructure automation workflows with more speed and simplicity.
In this guide, you will learn how to configure the LetsCloud MCP Server in Claude in a practical and secure way.
What is the LetsCloud MCP Server?
The LetsCloud MCP Server is a bridge between AI assistants and the LetsCloud platform.
In practice, it allows MCP-compatible clients, such as Claude, Cursor, Windsurf, and VS Code Copilot, to access LetsCloud infrastructure tools through a standardized connection.
Instead of interacting only with generic knowledge, the AI assistant can use real tools to retrieve account information, inspect available resources, and support cloud automation workflows.
You connect Claude to the LetsCloud MCP endpoint, authenticate with your LetsCloud API key, and start interacting with your infrastructure through prompts.
What can you do with the LetsCloud MCP Server in Claude?
After the configuration is complete, Claude can help with operations such as:
- Checking LetsCloud account information;
- Listing available locations;
- Viewing cloud instance plans;
- Checking available images for deployment;
- Listing existing cloud instances;
- Viewing details of a specific cloud instance;
- Working with SSH keys;
- Checking snapshots;
- Supporting automation and provisioning workflows.
The goal is not to remove human control, but to make repetitive infrastructure operations faster, clearer, and more conversational.
Prerequisites
Before you begin, make sure you have:
- An active LetsCloud account;
- Access to the LetsCloud dashboard;
- A LetsCloud API key;
- Claude Desktop installed;
- Access to the official LetsCloud MCP Server endpoint.
The MCP endpoint used for this integration is:
https://mcp.letscloud.io
The public LetsCloud MCP Server page is also available at:
Step 1: Generate your LetsCloud API key
The LetsCloud MCP Server uses API key authentication.
Access the LetsCloud dashboard, go to the API or account credentials area, and generate a new API key.
Keep this key secure, because Claude will use it to authenticate requests to the LetsCloud MCP Server.
Authentication uses the Bearer Token format:
Authorization: Bearer YOUR_LETSCLOUD_API_KEY
Never share your API key in public chats, repositories, screenshots, or documents accessible by third parties.
Step 2: Open the Claude Desktop configuration
Open Claude Desktop and go to:
Settings → Developer → Edit Config
This opens the claude_desktop_config.json file.
The file location depends on your operating system:
macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json
This file is where Claude Desktop stores MCP server configurations.
Step 3: Add the LetsCloud MCP Server entry
Inside claude_desktop_config.json, add the LetsCloud MCP Server entry under mcpServers.
Use the following structure:
{
"mcpServers": {
"letscloud": {
"url": "https://mcp.letscloud.io",
"headers": {
"Authorization": "Bearer YOUR_LETSCLOUD_API_KEY"
}
}
}
}
Replace YOUR_LETSCLOUD_API_KEY with the API key generated in your LetsCloud account.
If your configuration file already has other MCP servers, do not remove them. Add the letscloud entry inside the existing mcpServers object.
Example with multiple MCP servers:
{
"mcpServers": {
"another-server": {
"command": "npx",
"args": ["some-mcp-server"]
},
"letscloud": {
"url": "https://mcp.letscloud.io",
"headers": {
"Authorization": "Bearer YOUR_LETSCLOUD_API_KEY"
}
}
}
}
After editing the file, save it.
Step 4: Fully restart Claude Desktop
After saving the configuration file, fully quit Claude Desktop and open it again.
On macOS, make sure Claude is completely closed, not only minimized.
On Windows, close Claude Desktop completely before reopening it.
Restarting the application ensures that Claude reloads the MCP server configuration.
Step 5: Confirm the LetsCloud connection
Open a new chat in Claude Desktop.
Click the plug icon and confirm that letscloud appears as a connected MCP server.
If the connection is active, Claude should be able to access the tools exposed by the LetsCloud MCP Server.
You can test it with a simple prompt:
Show my LetsCloud account balance.
You can also try:
List the available LetsCloud locations.
Or:
Show my active LetsCloud cloud instances.
These first tests help confirm that authentication is working and that Claude can communicate with the LetsCloud MCP Server.
Step 6: Use more advanced prompts
Once the connection is validated, you can start using more complete prompts.
Example:
Analyze my LetsCloud cloud instances and show which ones are active, where they are located, and what information is relevant for an infrastructure review.
Another example:
List the available images for creating a new Ubuntu cloud instance and help me choose the best option for a development environment.
Or:
Check my LetsCloud SSH keys and organize a summary to make account administration easier.
The advantage of MCP is that Claude can use real tools and combine the returned information with contextual reasoning, instead of answering only with generic knowledge.
Example: Planning a new deployment
Imagine that you want to prepare a new cloud instance for a web project.
You could ask Claude:
I want to create a new LetsCloud cloud instance to host a Linux web application. Check the available locations, list compatible images, and suggest an initial configuration.
With the LetsCloud MCP Server connected, Claude can retrieve available information and help you structure the next step.
Depending on the available tools and permissions, it can also support more advanced workflows, such as provisioning, resource creation, and infrastructure organization.
Alternative: Using Claude Custom Connectors
Some Claude accounts may provide a Connectors or Custom Connectors interface for remote MCP servers.
If this option is available in your Claude account, you may be able to add the LetsCloud MCP Server directly through the Claude interface instead of editing the local configuration file.
Use the following information:
Name: LetsCloud MCP Server
URL: https://mcp.letscloud.io
Authentication: Bearer Token
Header: Authorization
Value: Bearer YOUR_LETSCLOUD_API_KEY
After saving the connector, start a new chat and confirm that the LetsCloud tools are available.
The exact name and availability of this feature may vary depending on the Claude version, plan, and platform.
What if the LetsCloud MCP Server does not appear in Claude?
If the letscloud MCP server does not appear in Claude Desktop, check the following:
- Make sure the JSON file is valid;
- Confirm that the entry was added under
mcpServers; - Verify that the API key is correct;
- Confirm that the URL is set to
https://mcp.letscloud.io; - Fully quit and restart Claude Desktop;
- Open a new chat after restarting;
- Check whether the plug icon shows the LetsCloud MCP server.
A common issue is invalid JSON formatting, such as missing commas, extra commas, or misplaced brackets.
If Claude Desktop already had other MCP servers configured, make sure the LetsCloud entry was added without replacing the existing configuration.
Security best practices
When connecting an AI assistant to your infrastructure, security should always come first.
Review actions before approving any execution. Even with a secure integration, the user remains responsible for validating commands, changes, and possible impacts on the environment.
Avoid pasting API keys into public conversations, shared documents, repositories, or screenshots. If you suspect that a key was exposed, revoke it immediately and generate a new one.
Start with read-only prompts before running actions that modify resources. This helps validate the connector behavior and understand how Claude interprets the data from your account.
It is also recommended to use clear and specific prompts. The more context you provide, the better the assistant can support your workflow.
Prompt examples for Claude
Here are some practical prompts you can try:
Show my LetsCloud account balance.
List my LetsCloud cloud instances and group them by status.
Show the available locations for creating a new cloud instance.
Which Linux images are available for deployment?
List my snapshots and show which cloud instance each one is related to.
Check my registered SSH keys and help me identify which ones are clearly named.
Help me plan a new cloud instance for a Node.js application with a database.
Analyze the available resources in my LetsCloud account and suggest an initial organization for development, staging, and production environments.
Why use the LetsCloud MCP Server with Claude?
The main advantage is turning infrastructure tasks into guided conversations.
Instead of switching between dashboard, documentation, scripts, and API calls, you can ask Claude to retrieve information, compare options, and support decision-making.
This makes the process more accessible for developers, operations teams, startups, and companies that want to accelerate cloud automation workflows.
The LetsCloud MCP Server also keeps the integration aligned with the modern AI ecosystem, where tools like Claude are no longer just text assistants, but intelligent interfaces for real systems.
Conclusion
Configuring the LetsCloud MCP Server in Claude is a practical way to bring intelligent automation to cloud infrastructure management.
With a few steps, you can connect Claude to your LetsCloud account and interact with resources such as cloud instances, snapshots, images, locations, SSH keys, and account information using natural language.
This integration is an important step for teams and developers looking for productivity, automation, and simplicity when managing cloud environments.
To get started, access the official LetsCloud MCP Server page, generate your API key, configure Claude Desktop, and connect Claude to the LetsCloud MCP endpoint.
0 COMMENTS