Celesto Cloud Computers
ai.celestoPublished by celesto.aiOfficial publisherv1.0.1Updated Oct 24, 2026
Hosted MCP for Celesto cloud computers: create, exec, ports, start/stop/delete.
Overview
A hosted MCP server for Celesto cloud computers that lets an assistant create, run commands on, expose ports for, start, stop, and delete them.
- What you can do
- Celesto Cloud Computers is a remote MCP endpoint that manages hosted cloud computers on the Celesto platform. According to the registry description, its tools cover creating a computer, executing commands on it, handling ports, and starting, stopping, or deleting it. It is a hosted service reached over streamable HTTP rather than a local package.
- When to use it
- Use it when an assistant needs to spin up and operate a cloud computer on Celesto — running commands or exposing ports — and to manage the lifecycle of those machines from a chat session. It suits users who already work with Celesto and want that control available to an AI assistant.
- Requirements
- A remote MCP endpoint at over streamable HTTP. Authentication is OAuth and is required; no environment variables or headers are declared. A Celesto account and network access are implied.
Installation
In SourceWeft
- Open Celesto Cloud Computers in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/ai.celesto%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"celesto-cloud-computers": {
"type": "http",
"url": "https://mcp.celesto.ai/mcp"
}
}
}Tools
0Version history
1- v1.0.1LatestOct 11, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.