Connect Claude Code to Alis Build.
Use this plugin to let Claude Code inspect Alis Build organisations, products, neurons, builds, deploys, and related workspace context.
- A preconfigured Claude Code MCP server for
https://mcp.alis.build - OAuth/OIDC sign-in through
https://identity.alisx.com - Alis Build tools available inside Claude Code after sign-in
- A standing Define → Build → Deploy primer loaded into every session, so Claude knows the workflow, how to route requests, and to run the
alisCLI — no trigger word required - When a session opens inside a
~/alis.build/<org>/build|define/…service folder, the package id and a pointer to its definitions ⇄ implementation counterpart are injected automatically - Claude Code approval prompts before tools perform sensitive actions
- The
alisCLI auto-approved in Claude Code, so command-line calls run without a permission prompt each time
You need:
- Claude Code installed and authenticated
- An Alis Build account with access to the organisations and products you want to use
- Network access to
https://mcp.alis.buildandhttps://identity.alisx.com
Add the Alis plugin marketplace:
claude plugin marketplace add alis-build/claude-plugin --sparse .claude-plugin plugins/alis-buildInstall the Alis Build plugin:
claude plugin install alis-build@alis --scope userStart Claude Code:
claudeFor a repository-shared install, use project scope:
claude plugin install alis-build@alis --scope projectIn Claude Code, run:
/mcp
Select the api MCP server for the alis-build plugin and complete the OAuth sign-in flow in your browser.
You should see api listed as a plugin-provided MCP server for alis-build. The sign-in flow opens https://identity.alisx.com in your browser.
After sign-in, ask Claude Code to use Alis Build:
build it
fix it
Use Alis Build to list the organisations I can access.
Show recent builds for product os in organisation alis.
Review the latest deploy logs for this neuron and suggest the next action.
Claude Code will ask before running tools that require approval.
The plugin auto-approves single, simple alis ... shell commands so the CLI runs without a permission prompt each time. For safety it only approves a lone invocation — anything that chains or redirects (|, &&, ||, ;, &, >, <, backticks, $(...)) falls through to Claude Code's normal permission flow. To restrict which subcommands are auto-approved, set ALIS_ALLOWED_SUBCMDS to a space-separated allowlist (e.g. ALIS_ALLOWED_SUBCMDS="define build deploy operations"); unset means every alis subcommand is approved.
This plugin includes Alis Build workflow commands:
/alis-build:build-it
/alis-build:fix-it
/alis-build:getting-started
Type build it to discover the right Alis Build skill for the thing you want to build. Type fix it to use the same discovery flow when the goal is framed as a fix. /alis-build:build-it and /alis-build:fix-it are slash-command shortcuts for the same router. /alis-build:getting-started uses the Alis Build getting-started skill for the platform workflow and simpleapi quickstart. If you installed or changed the plugin inside an already-running Claude Code session, run /reload-plugins.
If api does not appear in /mcp, confirm that the plugin install completed successfully:
claude plugin install alis-build@alis --scope userIf you installed or changed the plugin inside an already-running Claude Code session, reload plugins:
/reload-plugins
If sign-in fails, confirm that you can reach both https://mcp.alis.build and https://identity.alisx.com, then try /mcp again.