🚀 Cloudways MCP Server

Created By
aphraza year ago
Cloudways MCP Server
Overview

What is Cloudways MCP Server?

Cloudways MCP Server is a Model Context Protocol server designed for seamless integration with the Cloudways API, enabling AI assistants to manage Cloudways infrastructure.

How to use Cloudways MCP Server?

To use the Cloudways MCP Server, clone the repository, install dependencies, configure the environment, and start the server. It will be accessible at http://127.0.0.1:7000/mcp.

Key features of Cloudways MCP Server?

  • Security & Isolation: Encrypted data storage, auto-renewal of tokens, and rate limiting.
  • Performance & Reliability: Connection pooling, background token refresh, and graceful fallbacks.
  • Monitoring & Observability: Structured logging, real-time token health tracking, and customer analytics.

Use cases of Cloudways MCP Server?

  1. Managing server configurations and monitoring performance metrics.
  2. Accessing application details and credentials securely.
  3. Tracking customer usage patterns and system alerts.

FAQ from Cloudways MCP Server?

  • What operations does the MCP Server currently support?

The server currently supports read-only operations, with write operations planned for future releases.

  • What are the prerequisites for using the MCP Server?

You need Python 3.8+, a Redis server, and a Cloudways account with API access.

  • How can I monitor token status?

You can use built-in monitoring tools like get_token_status to check token health.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aphraz
Star
0
Language
Python
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago