Skip to main content
Glama

Heim MCP

Model Context Protocol server for Heim application deployment and management.

Overview

This MCP server allows AI agents like Claude Desktop, Cursor, Windsurf, and others to create, deploy, and manage Heim applications directly through natural language commands.

Purpose You can directly ask the AI to create new Heim applications from OpenAPI specifications, deploy them locally or to the cloud, and manage the Heim runtime.

What is Heim? Heim is a platform for creating and deploying backend applications.

Related MCP server: Hello World MCP Server

Available Tools

Tool

Description

new_heim_application

Creates a new Heim application from an OpenAPI 3.0.1 specification

deploy_heim_application

Deploys an application to the local Heim runtime (available at http://127.0.0.1:3000)

deploy_heim_application_to_cloud

Deploys an application to Heim cloud

start_heim

Starts the Heim runtime to handle deployment requests

clear_heim

Clears the local cache and stops the Heim runtime

update_heim

Updates Heim to the latest version

Using with Cursor

Installation - Globally

Run the MCP server using npx:

npx -y @nor2/heim-mcp@latest

In your Cursor IDE

  1. Go to Cursor Settings > MCP

  2. Click + Add New MCP Server

  3. Fill in the form:

    • Name: Heim (or any name you prefer)

    • Type: command

    • Command: npx -y @nor2/heim-mcp@latest

Installation - Project-specific

Add an .cursor/mcp.json file to your project:

{
  "mcpServers": {
    "heim": {
      "command": "npx",
      "args": [
        "-y",
        "@nor2/heim-mcp@latest"
      ]
    }
  }
}

Usage

Once configured, the Heim tools will be automatically available to the Cursor AI Agent. You can:

  1. Ask the AI to create new applications from OpenAPI specs

  2. Deploy applications locally or to the cloud

  3. Manage the Heim runtime

  4. The tools will be listed under Available Tools in MCP settings

Using with Roo Code

Access the MCP settings by clicking "Edit MCP Settings" in Roo Code settings or using the "Roo Code: Open MCP Config" command in VS Code's command palette.

{
  "mcpServers": {
    "heim": {
      "command": "npx",
      "args": [
        "-y",
        "@nor2/heim-mcp@latest"
      ]
    }
  }
}

Prerequisites

Before using this MCP server, you need to have Heim installed on your system. You can install it by following the instructions at https://heim.dev/releases/.

Development

# Install dependencies
pnpm install

# Build
pnpm build

Debugging the Server

To debug your server, you can use the MCP Inspector.

First build the server:

pnpm build

Run the following command in your terminal:

# Start MCP Inspector and server with all tools
npx @modelcontextprotocol/inspector node dist/index.js

License

MIT

Available Tools

6 tools
deploy_heim_applicationDeploy Heim ApplicationA
Idempotent

Runs 'heim deploy' command to deploy an application to a local Heim runtime. Which will make the application availible on http://127.0.0.1:3000 where is the path defined in your OpenAPI specification

Inputs: path.

deploy_heim_application_to_cloudDeploy Heim Application to CloudB
Idempotent

Runs 'heim deploy' command to deploy an application to Heim cloud. Which will make the application availible on the path outputted in the console

Inputs: path.

heim_clearA
Destructive

Clears the local cache of the Heim runtime which will attempt to stop the runtime and remove all applications, logs, metrics, etc. from the runtime.

Inputs: no named parameters.

heim_startB

Starts the Heim runtime which will run your backend applications.

Inputs: no named parameters.

heim_updateB

Updates Heim to the latest version.

Inputs: no named parameters.

new_heim_applicationNew Heim ApplicationA

Runs 'heim new' command on your local computer to create application schafholding from an OpenAPI 3.0.1 specification.

Inputs: path (required), openApiPath (required), name (required), language (required), +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. The tools cover deployment (local and cloud), runtime management (start, clear), system update, and application creation, with no overlap in functionality. An agent can easily distinguish between them based on their specific actions.

    Naming Consistency4/5

    The naming is mostly consistent with a verb_noun pattern, using underscores throughout. However, there is a minor deviation: 'new_heim_application' uses 'new' as a verb, while others like 'deploy_heim_application' use more standard action verbs, but this does not significantly hinder readability or predictability.

    Tool Count5/5

    With 6 tools, the count is well-scoped for managing a Heim application lifecycle. Each tool earns its place by covering key operations such as deployment, runtime control, updates, and application creation, without being overly sparse or bloated.

    Completeness4/5

    The tool set provides good coverage for the Heim domain, including deployment (local and cloud), runtime management, updates, and application creation. A minor gap exists in monitoring or logging tools, but core workflows are well-supported, allowing agents to perform essential tasks without significant dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      C
      quality
      Not graded
      maintenance
      A simple boilerplate MCP server that provides a basic greeting tool for demonstration purposes. Serves as a starting template for developers to quickly create and deploy custom MCP servers.
      1
      10 npm
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server starter with authentication, observability, and a plugin system for building and deploying MCP servers quickly.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Dynamic MCP server for Node.js enabling runtime tool creation, management, and execution in isolated sandboxes (Docker or Node).
      8
      11 npm
      1
      MIT