Rqeim Cloud

com.rqeimPublished by rqeim.comOfficial publisherv1.0.0Updated Nov 14, 2026

Deploy, preview and diagnose the apps on your Rqeim Cloud account.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Connects an AI assistant to a Rqeim Cloud account so it can create, deploy, preview and diagnose the account's hosted applications.

What you can do
  • Read projects, environments, health and deploy history
  • Create environments and open a sandboxed copy of a project to change code, preview and publish it
  • Read environment logs and run scheduled jobs
  • Restore a backup or delete an environment, with explicit confirmation
  • Follow background changes through task keys and read the service's workflow guide
When to use it
Useful when your apps are hosted on Rqeim Cloud and you want an assistant to inspect deploys, read logs, spin up environments or preview changes without switching to the dashboard.
Requirements
A remote streamable HTTP endpoint; no local package. A Rqeim Cloud account signed in through OAuth 2.1 with dynamic client registration and PKCE, or an account API token sent as an Authorization Bearer header. Network access to the service.
Before you install
Tools can change real infrastructure: creating or deleting environments, publishing code, running jobs and restoring backups. Destructive or production tools need an explicit confirm flag, and production changes are meant to go through an environment first. The server acts only on the signed-in account, and one project belongs to one account with no shared workspaces.

Installation

In SourceWeft

  1. Open Rqeim Cloud in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/com.rqeim%2Fcloud/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rqeim-cloud": {
      "type": "http",
      "url": "https://cloud.rqeim.com/mcp"
    }
  }
}

README

Rqeim Cloud MCP

Connect an AI agent to Rqeim Cloud and it can create, deploy, inspect and diagnose the applications on your account: environments, previews, logs, domains, health and backups.

This repository is the public distribution bundle for the Rqeim Cloud MCP server. It contains no server code: the server is hosted at https://cloud.rqeim.com/mcp.

1. What the server does

Rqeim Cloud runs Docker applications from a Git repository: you push, it deploys. With this server an agent works the same way a person does in the dashboard:

  • read the account's projects, environments, health and deploy history;
  • open a copy of a project, change its code in a sandboxed machine, preview it, and publish it;
  • read logs, run scheduled jobs, restore a backup (with explicit confirmation).

Every change is asked for explicitly by the person in the conversation. The server never decides on its own to deploy, delete, or touch production.

2. Connect

Claude Code

bash
claude mcp add --transport http rqeim-cloud https://cloud.rqeim.com/mcp

Or install the plugin, which also adds the workflow skill:

bash
claude plugin marketplace add Rqeim/rqeim-cloud-mcpclaude plugin install rqeim-cloud@rqeim

Claude Code opens a browser to sign in to your Rqeim account the first time.

Gemini CLI

bash
gemini extensions install https://github.com/Rqeim/rqeim-cloud-mcp

ChatGPT and Claude (web, desktop, mobile)

Add a connector with the URL https://cloud.rqeim.com/mcp/directory and sign in when asked. /mcp/directory lists every tool by name, which is what a public directory reviews; the plain /mcp keeps the short list and its search for agents. Each door has its own OAuth resource.

Codex and other MCP clients

Streamable HTTP at https://cloud.rqeim.com/mcp, OAuth 2.1 with dynamic client registration and PKCE. An account API token works too, as Authorization: Bearer <token>.

3. Authentication

The server signs users in with OAuth 2.1, discovered from the standard well-known documents:

DocumentURL
Protected resource metadata (RFC 9728)https://cloud.rqeim.com/.well-known/oauth-protected-resource/mcp
Authorization server metadata (RFC 8414)https://cloud.rqeim.com/.well-known/oauth-authorization-server

Clients register themselves (/oauth/register), use PKCE with S256, and receive a token scoped to mcp alone. A token is an hour long, refreshed without a new sign-in.

An unauthenticated request answers:

http
HTTP/1.1 401 UnauthorizedWWW-Authenticate: Bearer realm="rqeim-cloud", resource_metadata="https://cloud.rqeim.com/.well-known/oauth-protected-resource/mcp", scope="mcp"

4. Tools

Every tool is one intent. Reads change nothing and answer without confirmation; tools that change something take a requestId (generated when omitted) and destructive or production tools also need confirm: true after the person agrees. A change runs in the background and returns a task key: follow it with get_task.

Naming: list_projects, get_project, get_projects_health, create_environment, workspace_shell, read_environment_logs, finish_task, delete_environment, get_task, read_guide.

Run read_guide once per conversation: it is the current, complete description of the workflow and the rules (written for the model, kept up to date by the service).

5. Data and privacy

The server reads and writes only the account that signed in. It stores no conversation content and returns no telemetry identifiers in tool results. See PRIVACY.md.

6. Limits

  • One project belongs to one account; there are no shared workspaces.
  • Machine operations (deploy, build, restore) are asynchronous: a redeploy is 10–40 seconds, a first deploy about a minute.
  • Production is read-and-diagnose for agents: a change goes through an environment first, then a deploy.

7. Support

Source: README.md at commit bd57326

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 14, 2026

Score

85% 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
  • License10 pts