Gheima

io.github.gheimaPublished by GitHub account gheimav0.3.0Updated Oct 31, 2026

Deploy and run apps, databases and storage on the Gheima platform, billed in MAD.

VerifiedStreamable HTTPWeb executableDatabasesCloud & Infrastructure

Overview

AI-generated overview

Connects an assistant to the Gheima platform to deploy and run apps, databases and storage, billed in MAD.

What you can do
  • Deploy and run applications on the Gheima platform
  • Provision and manage databases and storage
  • Read platform credentials when explicitly enabled
  • Change platform resources when writes are explicitly enabled
  • No tool list is published, so exact operations are not documented here.
When to use it
Use it when you host apps, databases or storage on Gheima and want an assistant to help deploy or manage those resources from a chat session.
Requirements
A Gheima account with OAuth sign-in, or a GHEIMA_API_KEY (optional after a local gheima login). Available as a remote endpoint or as the npm package @gheima/mcp over stdio, which needs Node.js. Network access to the platform.
Before you install
Tools that read credentials are off unless GHEIMA_MCP_ALLOW_SECRETS is set to 1; tools that change anything are off unless GHEIMA_MCP_ALLOW_WRITES is set to 1. Enabling writes lets the assistant create, change or delete platform resources, and usage is billed in MAD, so costs can accrue. Treat the API key as a secret.

Installation

In SourceWeft

  1. Open Gheima in the dashboard and add it to a workspace.
  2. Connect the required 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/io.github.gheima%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gheima": {
      "type": "http",
      "url": "https://gheima.ma/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.3.0LatestOct 31, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.