imperal-mcp
OfficialBuild, validate, deploy, and operate cloud apps on Imperal Cloud directly from an AI agent using these capabilities:
validate_ir— Validate anapp.ir.jsonspecification against the live Imperal schema, returning a{valid, issues}report before deploying anything.smoke_ir— Smoke-test a single function in an isolated sandbox, returning{ok, result, trace}for debugging.deploy_ir— Deploy a complete app IR to your Imperal account (auto-creates the app record if needed), making it live instantly.list_apps— List all developer apps in your Imperal account (with PII masking applied).get_app— Retrieve a specific app's full manifest and available tools, with PII masking.run_read_tool— Execute a read-only tool on a deployed app to query live data; write/destructive operations are refused for safety.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@imperal-mcpvalidate and deploy my app.ir.json"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
imperal-mcp
Build, ship, and run real cloud apps on Imperal — straight from your AI agent.
imperal-mcp puts the app-building power of Imperal Cloud — the ICNLI AI Cloud OS that Webbee 🐝 runs on — inside any MCP-capable agent. Connect it to Claude, Claude Code, Codex, Cursor, Gemini CLI, Cline, Windsurf, or Goose, sign in with your own Imperal account, and your agent can design, deploy, and operate real cloud apps for you — data, logic, and UI included — without ever leaving the chat.
You describe what you want. Your agent builds it. Imperal runs it.
What you can do
Tell your agent what you want — and it builds it on Imperal, end to end:
Design an app from a description — its data/entities, the functions that act on them, and the UI panels that render them, as one clean declarative spec.
Validate it instantly against the live Imperal schema, before anything ships.
Smoke-test a function in an isolated sandbox and see it actually work.
Deploy it live to your Imperal account — instantly available, fleet-wide.
List & inspect every app you've built.
Run your apps — query their data through their own tools, right from the agent.
Apps your agent can build in a single flow:
a habit / workout / reading tracker with list + detail views
a personal CRM or contacts book
a snippet vault or bookmark manager
a lightweight expense or invoice log
a notes / tasks / journal app
…any data-backed app with screens and actions you can describe in plain words.
Related MCP server: Laminar MCP Server
How it works
Your client's own LLM authors the app; imperal-mcp gives it the rails. It reads the IR spec and worked examples, validates the draft against the live schema, smoke-tests it, and deploys it to the cloud — no hand-written deployment scripts, no YAML wrangling. The heavy lifting — orchestration, hosting, scaling, the kernel — is Imperal's. Your agent just describes the app; the kernel makes it real.
Quick-add to your agent
Client | One-liner |
Cursor | |
Claude Code |
|
Everything else |
Install
imperal-mcpand sign in first — see below.
Install & sign in
pipx install imperal-mcp # or: pip install --user imperal-mcp
imperal-mcp login # opens your browser to sign in to Imperallogin stores credentials in ~/.imperal/credentials.json and auto-refreshes your access token — no manual token management. Sign out any time:
imperal-mcp logoutThat's it — every supported client uses the same imperal-mcp binary and the same stored sign-in.
Your first app (60 seconds)
Install +
imperal-mcp login(above), and add it to your agent.Ask your agent, in plain language:
"Build me a habit tracker — I want to add habits, mark them done each day, and see today's summary. Then deploy it."
Your agent authors the app, validates it, smoke-tests a function, and deploys it to your Imperal account. It comes back with the live app and its tools — ready to use.
Want to iterate? Just keep talking: "add a weekly streak view", "now build me an expense tracker too."
Per-client config
All clients use the same installed binary — imperal-mcp — and the same credentials from imperal-mcp login.
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"imperal": { "command": "imperal-mcp" }
}
}Claude Code
/plugin marketplace add imperalcloud/imperal-mcp
/plugin install imperal-mcp@imperalOr add directly to your project .mcp.json:
{
"mcpServers": {
"imperal": { "command": "imperal-mcp" }
}
}Cursor
Click the Add to Cursor button above, or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"imperal": { "command": "imperal-mcp" }
}
}Codex (OpenAI)
Add to ~/.codex/config.toml:
[mcp_servers.imperal]
command = "imperal-mcp"Gemini CLI
{
"mcpServers": {
"imperal": { "command": "imperal-mcp" }
}
}Cline
In VS Code, add to Cline's MCP server list:
{
"imperal": { "command": "imperal-mcp", "disabled": false }
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"imperal": { "command": "imperal-mcp" }
}
}Goose (Block)
Add a StandardIO extension in Goose settings:
{ "type": "stdio", "name": "imperal", "cmd": "imperal-mcp", "args": [] }Tools
Tool | What it does |
| Validate an |
| Run one function in an isolated store and report |
| Deploy an app into your account (creates the app record if needed) — live instantly. |
| List your developer apps. |
| Get one app's manifest + tools. |
| Run one of a deployed app's read tools to fetch its data. |
Resources
URI | Description |
| The IR specification — structure, fields, action vocabulary. |
| All |
| A worked |
Prompt
build_imperal_app — step-by-step guidance for an LLM to go from intent to a deployed app: read the spec, author the IR, validate, smoke-test, deploy.
Configuration
Variable | Default | Purpose |
|
| Auth / API base URL |
|
| Panel base URL |
| (not set) | Optional token for CI / headless use — set it to skip browser login |
For CI or headless environments, set IMPERAL_TOKEN to a token from panel.imperal.io → Developer → Access tokens.
Privacy & security
You sign in with your own Imperal account (browser OAuth). Credentials live locally at ~/.imperal/credentials.json (0600) and refresh automatically — nothing is shared with third parties and there's no telemetry. Read responses are PII-masked before they reach the LLM. Full details: PRIVACY.md.
Links
Imperal Cloud — https://imperal.io
Panel (your apps, tokens, billing) — https://panel.imperal.io
ICNLI (the open protocol behind it, CC BY-SA) — https://icnli.org
Development
git clone https://github.com/imperalcloud/imperal-mcp
cd imperal-mcp
pip install -e '.[dev]'
python -m pytestBuilt on Imperal Cloud — the AI Cloud OS. 🐝
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/imperalcloud/imperal-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server