CloudHike

dev.cloudhikePublished by cloudhike.devOfficial publisherv1.0.0Updated Oct 29, 2026

A full backend your AI coding agent can set up over MCP

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

CloudHike is a remote MCP endpoint that lets an AI coding agent set up and manage a full backend for a project.

What you can do
  • Set up and manage a complete backend for a project from the coding agent, as described by the provider.
  • No individual tools are listed in the manifest, so the exact operations available are not documented here.
  • Access is tied to a workspace API key, suggesting backend resources are scoped to a workspace account.
When to use it
Consider it when you want an AI coding agent to stand up backend infrastructure for an app without leaving the agent, and you already have or are willing to create a CloudHike workspace.
Requirements
A remote MCP connection to the CloudHike endpoint over streamable HTTP. A required bearer token sent in the Authorization header, using a workspace API key obtained from the CloudHike dashboard. Network access to the provider.
Before you install
The server requires a workspace API key as a bearer token; treat it as a secret and keep it out of shared logs or transcripts. The provider describes it as setting up a full backend, so expect it to create and change resources in your workspace, which may incur costs. Tool-level behavior is not documented in the supplied material, so review what it does before granting access.

Installation

In SourceWeft

  1. Open CloudHike in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/dev.cloudhike%2Fcloudhike/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.

{
  "mcpServers": {
    "cloudhike": {
      "type": "http",
      "url": "https://cloudhike.dev/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.