Heim MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| new_heim_applicationA | Runs 'heim new' command on your local computer to create application schafholding from an OpenAPI 3.0.1 specification. |
| deploy_heim_applicationA | 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 |
| deploy_heim_application_to_cloudB | Runs 'heim deploy' command to deploy an application to Heim cloud. Which will make the application availible on the path outputted in the console |
| heim_startB | Starts the Heim runtime which will run your backend applications. |
| heim_clearA | 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. |
| heim_updateB | Updates Heim to the latest version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.