MCP Server Setup
The @reoclo/theta MCP server lets AI coding tools manage your Reoclo infrastructure directly — servers, applications, deployments, domains, logs, monitors, status pages, and scheduled operations.
Prerequisites
Section titled “Prerequisites”- An API key — create an Integration Key from API Keys in the dashboard. See API Keys for details.
- Node.js 18+ — required to run the MCP server via
npx.
Claude Code
Section titled “Claude Code”CLI (recommended)
Section titled “CLI (recommended)”claude mcp add reoclo -e REOCLO_API_KEY=rk_t_your_key_here -- npx -y @reoclo/thetaThis registers the server immediately. Restart Claude Code to pick it up.
Config file
Section titled “Config file”Add to .mcp.json in your project root (or ~/.claude/mcp.json for global access):
{ "mcpServers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "${REOCLO_API_KEY}" } } }}Verify
Section titled “Verify”In Claude Code, type:
/mcpYou should see reoclo listed with its tools. Try asking: “List my servers” or “Show recent deployments”.
Cursor
Section titled “Cursor”Add to .cursor/mcp.json in your project root:
{ "mcpServers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "rk_t_your_key_here" } } }}Restart Cursor after saving. The MCP server appears in Settings > MCP once connected.
Windsurf
Section titled “Windsurf”Add to ~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "rk_t_your_key_here" } } }}Restart Windsurf. Cascade will pick up the server and list available tools automatically.
VS Code (GitHub Copilot)
Section titled “VS Code (GitHub Copilot)”VS Code supports MCP servers through GitHub Copilot Chat (agent mode). Add to .vscode/mcp.json in your project root:
{ "servers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "${REOCLO_API_KEY}" } } }}VS Code supports ${VAR} syntax and will read from your shell environment.
After saving, open Copilot Chat in agent mode (@workspace or the agent panel) — the Reoclo tools will be available.
Add to your Zed settings (~/.config/zed/settings.json):
{ "context_servers": { "reoclo": { "command": { "path": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "rk_t_your_key_here" } } } }}Restart Zed. The server will appear in the Assistant panel’s context server list.
JetBrains (IntelliJ, WebStorm, PyCharm, etc.)
Section titled “JetBrains (IntelliJ, WebStorm, PyCharm, etc.)”JetBrains IDEs support MCP through AI Assistant. Add to .idea/mcp.json in your project root:
{ "mcpServers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "rk_t_your_key_here" } } }}Restart the IDE. The MCP server will be available in the AI Assistant tool window.
Add via the Cline MCP settings UI (Cline > MCP Servers > Add), or edit your config directly at ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json (macOS) or the equivalent path on your OS:
{ "mcpServers": { "reoclo": { "command": "npx", "args": ["-y", "@reoclo/theta"], "env": { "REOCLO_API_KEY": "rk_t_your_key_here" } } }}After saving, Cline will show a connection indicator next to the server name. Click it to verify the tools loaded.
Other MCP Clients
Section titled “Other MCP Clients”Any MCP-compatible client can use the server. Run it directly:
REOCLO_API_KEY="rk_t_your_key_here" npx -y @reoclo/thetaThe server communicates over stdio using the Model Context Protocol. Point your client at this command and it will discover tools automatically.
Available Tools
Section titled “Available Tools”The tools registered depend on your API key’s permissions. A key with read-only access will only see read tools.
| Category | Tools |
|---|---|
| Servers | list_servers, get_server, get_server_metrics, get_server_health, check_server_health, list_containers, inspect_container, restart_container, port_scan |
| Applications | list_applications, get_application, get_app_config, update_app_config, trigger_deploy |
| Deployments | list_deployments, get_deployment, get_deployment_logs, get_deployment_stages, get_deployment_build_log |
| Domains | list_domains, get_domain, get_dns_overview, check_domain_health, add_domain, verify_domain |
| Logs | search_logs, live_logs, get_system_logs, get_log_usage, get_server_log_sources, get_log_stats |
| Monitors | list_monitors, get_monitor, create_monitor, update_monitor |
| Status Pages | list_status_pages, get_status_page, create_incident, update_incident |
| Scheduled Ops | list_scheduled_operations, get_scheduled_operation, create_scheduled_operation, trigger_scheduled_operation |
| Other | whoami, list_repositories, list_env_vars, set_env_var, get_dashboard, get_audit_log |
Configuration
Section titled “Configuration”| Variable | Required | Description |
|---|---|---|
REOCLO_API_KEY | Yes | Your Integration Key (starts with rk_t_) |
REOCLO_API_URL | No | API endpoint override (defaults to https://api.reoclo.com/mcp) |
Troubleshooting
Section titled “Troubleshooting”Server not appearing
Section titled “Server not appearing”- Verify Node.js 18+ is installed:
node --version - Test the server manually:
REOCLO_API_KEY="rk_t_..." npx -y @reoclo/theta - Check your editor restarted after config changes
No tools listed
Section titled “No tools listed”- Verify the API key is valid and not revoked
- Check the key has permissions for the resources you expect (a Read Only key won’t show write tools)
- Run
whoamithrough the MCP server to confirm the key’s permission scope
Authentication errors
Section titled “Authentication errors”- Ensure the key starts with
rk_t_(Integration Key prefix) - Check for trailing whitespace or newlines in the key value
- Verify the key hasn’t expired (check API Keys in the dashboard)
Next Steps
Section titled “Next Steps”- API Keys to create and manage keys
- API Overview for direct API access
@reoclo/thetaon npm for the full package documentation