MCP server
Connect Claude or any MCP client to REM CloudHub with your token, pick the server for your task, and understand levels, confirm codes and the access policy.
REM CloudHub serves its tools over the Model Context Protocol (streamable HTTP). An AI client connected with your token can inspect and operate your projects, jobs, databases, files, AI keys and agents, with your rights and nothing more. More than 700 tools are grouped into servers.
Servers
Server | Address | Tools for |
|---|---|---|
Everything |
| Every tool you may use |
Apps |
| Projects end to end: create, deploy, inspect, diagnose, logs, metrics, env, jobs |
Git |
| Repositories through the git proxy: branches, commits, pull requests |
Resources |
| Databases, the warehouse, services, AI keys |
Files |
| List, inspect, upload, share files |
Vault |
| Secrets metadata only: which exist, where they are bound, when they changed |
Context |
| Knowledge collections, search, ask, memories |
Agents |
| Plan, create, run, pause and stop agents; read run traces; answer approvals |
Sandbox |
| Your own sandboxes: run commands, ports, stop |
Skills, MCPs, Your MCP servers |
| Agent skills; the MCP catalogue; your own servers |
Governance, Audit |
| Access, approvals, the production gate, the audit trail |
Jira, Notifications, Feedback, H Panel |
| Tickets under your organisation's policy, the bell, feedback threads, health and uptime |
https://remcloudhub.com/mcp/healthz lists the servers without signing in. Three tools are on every server: whoami (who the token is), find (search everything you can see) and qch_navigate (the console page for a thing). A smaller server gives a model fewer, more relevant tools: prefer /mcp/apps for deploy work.
Connect
Make a personal token (qchp_) and bind it to the mcp area plus the areas the tools need (or leave areas empty).
Claude Code
claude mcp add --transport http remcloudhub https://remcloudhub.com/mcp/apps \
--header "Authorization: Bearer $RCH_TOKEN"Any client that reads an mcpServers file (Claude Desktop, IDE assistants), through the mcp-remote bridge:
{
"mcpServers": {
"remcloudhub": {
"command": "npx",
"args": ["mcp-remote", "https://remcloudhub.com/mcp/apps",
"--header", "Authorization: Bearer ${RCH_TOKEN}"],
"env": {"RCH_TOKEN": "qchp_..."}
}
}
}Python (official MCP SDK)
import asyncio, os
from mcp import ClientSession
from mcp.client.streamable_http import streamablehttp_client
async def main():
headers = {"Authorization": f"Bearer {os.environ['RCH_TOKEN']}"}
async with streamablehttp_client("https://remcloudhub.com/mcp/apps", headers=headers) as (r, w, _):
async with ClientSession(r, w) as s:
await s.initialize()
print(await s.call_tool("whoami", {}))
print(await s.call_tool("deploy_status", {"app": "pricing-api"}))
asyncio.run(main())To act in another organisation, add the X-RCH-Org header with its uid.
What a model can see and do
tools/listshows only the tools your role level reaches and your token may call. Levels: member, team admin, platform admin, super admin. A level only hides a tool; every call still runs the same permission checks as the console.Write tools never run on a model's word alone. The first call answers a preview and a
confirm_code; the tool runs when called again with the same arguments plus that code, within 120 seconds. Show the preview to the person before confirming.Your organisation's MCP access policy can allow, require confirmation for, or deny any tool, per person, group, role, token or service account. A refusal names the rule.
Secret values are never returned.
vault_revealis denied by default and, where a policy allows it, also needs a fresh password confirmation.Every decision is recorded in the audit trail with the tool, the token and the outcome.
Some useful tools
Tool | Does |
|---|---|
| Read a project's state, latest deploy, logs and metrics; explain a failure |
| Create, deploy, restart, pause or resume a project (write: preview first) |
| Set environment variables and bind secrets |
| Jobs |
| What an error code means; what happened under a reference |
| What needs you now |
Errors
Answer | Meaning |
|---|---|
| No token, or an unknown, expired or revoked one. An expiring token gets |
| The token's binding does not allow this server or area |
Tool error naming a rule | The access policy refused it |
Confirm code expired | Call again for a new preview |