PluginBench
MCP Server
Active
MIT

Contabo (VPS) MCP Server MCP Server

ai.com.mcp/contabo

Turn Contabo's VPS API into AI-ready MCP tools instantly—no rewrites, full API control.

RepositoryRegistry
How to choose

What this kind of tool is for

  • Automate a build, test, or deployment step you repeat by hand.
  • Review or refactor code in an existing repository without leaving your agent.
  • Bridge an internal service or CLI into the agent toolset.

How to compare servers like this

Scope of control:
Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
Environment fit:
Match the runtime it expects (Node, Python, a container) to what you actually run.
Maintenance signal:
Check the last-commit date — dev tooling that lags upstream breaks first.
Config surface:
Prefer tools whose environment-variable or config keys are documented plainly.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the Contabo (VPS) MCP Server MCP server?

The Contabo MCP Server exposes Contabo's cloud provisioning and VPS management API as Model Context Protocol tools, enabling AI agents to automate infrastructure tasks. Built on HAPI MCP, it transforms the Contabo OpenAPI specification into agent-ready capabilities without modifying the underlying API logic.

This server bridges Contabo's VPS management API and AI agents via the Model Context Protocol. It lets Claude, ChatGPT, and other MCP clients provision, configure, and manage Contabo cloud resources programmatically. Use it to automate infrastructure workflows, scale deployments, and integrate cloud operations into agentic systems—all while maintaining your existing API governance, auth, and audit trails.

How to install Contabo (VPS) MCP Server

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • Authorization
    required
    secret

    Bearer token for authenticating with the Contabo API. Obtain via the documented token endpoint.

  • x-request-id

    Optional request ID for tracing (recommended for support/debugging)

~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "contabo": {
      "url": "https://contabo.run.mcp.com.ai/mcp"
    }
  }
}

Use cases

  • Automate VPS provisioning and teardown via natural language commands
  • Manage Contabo cloud resources from Claude or ChatGPT without leaving the chat
  • Build agentic infrastructure workflows that scale and configure servers on demand
  • Integrate Contabo operations into multi-tool orchestration pipelines with OrcA
  • Query and monitor VPS status, billing, and resource allocation through AI agents

Contabo (VPS) MCP Server MCP server FAQ

What is the Contabo MCP Server?

It's an MCP server that exposes Contabo's VPS and cloud provisioning API as tools for AI agents. Built on HAPI MCP, it automatically transforms Contabo's OpenAPI specification into agent-ready capabilities.

Do I need to rewrite my Contabo API integration?

No. HAPI MCP lifts your existing Contabo OpenAPI spec directly into MCP tools. Your authentication, validation, and business rules remain unchanged.

Which AI clients can use this server?

Any MCP-compatible client: Claude, ChatGPT, QBot, chatMCP, and custom orchestrators. It's vendor-neutral by design.

How do I install and connect it?

The server is available as a remote MCP endpoint at https://contabo.run.mcp.com.ai/mcp. Configure your MCP client to connect to this URL, or install the HAPI CLI locally and run `hapi serve` with your Contabo API spec.

Is authentication handled?

Yes. Your Contabo API credentials and permissions flow through automatically. HAPI inherits auth, rate limits, and audit logs from your API layer—no shadow logic.

What can I automate with this server?

VPS provisioning, configuration, scaling, monitoring, billing queries, and resource management—any operation exposed by Contabo's API becomes an AI-callable tool.

README (reference)

Source of truth, from the repository.

HAPI MCP – Headless API for Model Context Protocol

Stop rewriting systems for AI. Instantly turn your APIs into MCP servers.

HAPI MCP lifts your OpenAPI catalog into MCP tools automatically, keeping design (OAS/Arazzo) and runtime (agents/LLMs) cleanly separated. Your existing APIs become AI-ready tools—no new business logic, no sidecar servers, no rework.

Key Features

  • No rewrites: Reuse 100% of your API logic. OpenAPI in, MCP tools out. No parallel codebase or shadow services.
  • Faster time-to-value: Turn specs into agent-ready tools in minutes. Update the spec, ship new tools instantly.
  • Reduced risk: Permissions, auth, rate limits, auditability are inherited from your APIs—governance without bolt-ons.
  • Scales with you: runMCP delivers serverless-like elasticity with long-running when needed. Cold-start fast, stay warm for throughput.
  • Deterministic orchestration: OrcA plans and executes multi-tool tasks predictably—no brittle prompt chaining.
  • Vendor-neutral: Works with any MCP client: ChatGPT, Claude, QBot, chatMCP. OAS + MCP + Arazzo stay portable.

How It Works

  1. Pick your API spec

    • OpenAPI, Swagger, REST—HAPI CLI works with any API specification format.
    • Supports OpenAPI 3.0+, REST APIs, OAuth 2.0 Dynamic Client Registration.
  2. Run a single command

    • One simple CLI command transforms your API into a usable MCP Server.
    • No complex setup, zero configuration, works anywhere, cross-platform.
  3. Use instantly

    • Your API is now ready as a tool, AI agent, or testing interface.
    • MCP server ready, AI agent compatible, testing interface, developer experience friendly.

Visual Pipeline

API Spec (swagger.json) → HAPI CLI → Usable Tool (AI-ready) ← MCP Clients
[ OpenAPI / Swagger ]       [ HAPI CLI ]        [ MCP Server ]
       (Your API)         →   (Transform)   →   (Usable Tool)
                                                 ↑          ↑
                                                 |          |
                                          [ ChatGPT ]  [ runMCP ]
                                          [ Claude  ]  [ OrcA   ]
                                          [ QBot    ]  [ chatMCP]
                                          [ Agents  ]

Who Wins With HAPI

  • Executives: Ship AI initiatives without ballooning cost. Keep teams focused on outcomes, not rewrites and integration sprawl.
  • Architects & PMs: Design with OpenAPI/Arazzo, run with MCP. Clear contracts, policy inheritance, and versioned workflows keep risk low.
  • Engineers & Ops: Deploy once. HAPI Server + runMCP scale tools; QBot/chatMCP give fast feedback; OrcA keeps executions deterministic.

Your Stack, Already Wired

  • HAPI Server: Turns OpenAPI into MCP tools automatically—contracts stay in sync with your source of truth.
  • runMCP: Autoscaling execution and testing for MCP tools; cold-start fast, stay warm when workflows run long.
  • QBot: CLI TUI for power users to interact with MCP tools directly from terminal or scripts.
  • chatMCP: Conversational client that speaks MCP natively for support, ops, and internal assistants.
  • OrcA: Deterministic planning and orchestration for multi-tool tasks; no brittle prompt spaghetti.
  • Agents: Build agentic systems from standard APIs—no custom glue. Connect MCP clients across platforms.

Demos

Documentation

FAQ

  • Do we need to rewrite our services?
    No. HAPI MCP lifts your existing OpenAPI specs directly into MCP tools. Your auth, validation, and business rules remain unchanged.

  • Is this just another MCP server?
    It’s the Headless API model: your API becomes the runtime. HAPI Server reflects it as MCP; runMCP scales it; OrcA orchestrates it. No duplicate logic.

  • Which clients can consume the tools?
    Any MCP client: ChatGPT, Claude, QBot, chatMCP, bespoke orchestrators—vendor-neutral by design.

  • How do we keep control and compliance?
    Your API remains the single source of truth. Policies, RBAC, rate limits, and audit logs flow through automatically; no shadow logic.

  • What about security and privacy?
    Scoped credentials, per-tool permissions, and auditable calls are inherited from your API layer. HAPI adds guardrails and observability for regulated environments.

  • How fast can we get started?
    You can transform your first API into an MCP tool in less than five minutes. The HAPI CLI makes it quick and painless.

Get Started

  1. Install HAPI CLI from latest release: https://github.com/la-rebelion/hapimcp/releases

  2. Transform your OpenAPI spec into an MCP server with a single command:

    hapi serve path/to/your/swagger.json --headless
    
  3. Start using your MCP tools with any compatible client!

  4. Explore the documentation for advanced usage and best practices.

Contributing

Contributions are welcome! Open a discussion or submit a pull request on GitHub: https://github.com/la-rebelion/hapimcp

License

HAPI MCP is licensed under the MIT License. See LICENSE for details.

Related MCP servers

HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants

View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

9
HTML
MIT
View repository →

Turn LinkedIn's API into AI-ready MCP tools—retrieve profiles and publish content instantly.

9
HTML
MIT
View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no parallel codebases.

9
HTML
MIT
View repository →

Transform OpenAPI specs into MCP tools instantly—no rewrites, no sidecar servers.

9
HTML
MIT
View repository →

Official MCP Registry: publish and discover MCP servers like an app store for AI agents.

7.3k
Go
View repository →