imperal-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IMPERAL_TOKEN | Yes | Your Imperal access JWT token. Obtain from panel.imperal.io → Developer → Access tokens. | |
| IMPERAL_API_URL | Yes | The URL of the Imperal API server (e.g., https://auth.imperal.io) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_irC | Validate an app.ir.json locally (envelope + every declarative step). |
| smoke_irA | Run one function of an app.ir.json in an ISOLATED store and report {ok,result,trace}. |
| deploy_irA | Deploy an app.ir.json into the caller's account (creates the app record if needed). |
| list_appsA | List the caller's developer apps (PII-masked). |
| get_appA | Get one app's manifest + tools (with action_type) (PII-masked). |
| run_read_toolB | Run a READ-only tool of a deployed app (refuses write/destructive). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| build_imperal_app | Guidance for building an Imperal app from intent. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| _r_spec | |
| _r_ui | |
| _r_ex |
TDQS
Scored across 6 tools
Each tool targets a distinct action: deploy, get, list, run read-only, smoke test, and validate. No overlapping purposes.
Most tools follow verb_noun pattern (deploy_ir, get_app, list_apps, validate_ir), but 'run_read_tool' uses an adjective and 'smoke_ir' uses an unconventional verb, creating minor inconsistency.
With 6 tools, the server covers key operations for managing IR-based apps without being overwhelming. The scope is well-balanced.
Core workflows are covered (validation, deployment, listing, reading), but missing update/delete for apps and any write tool execution, leaving notable gaps for full lifecycle management.