Alis Build Codex Plugin

Connect Codex to Alis Build.

Use this plugin to let Codex inspect Alis Build organisations, products, neurons, builds, deploys, and related workspace context.

What You Get

• A preconfigured Codex MCP server for https://mcp.alis.build
• A preconfigured Alis Build OAuth client and scopes for MCP sign-in
• OAuth/OIDC sign-in through https://identity.alisx.com
• Alis Build tools available inside Codex after sign-in
• Alis Build tools available without per-call MCP approval prompts
• Workspace-aware context injection through Codex hooks

Before You Start

You need:

• Codex CLI or the Codex IDE extension
• An Alis Build account with access to the organisations and products you want to use
• Network access to https://mcp.alis.build and https://identity.alisx.com

Install

Install the Alis Build plugin and sign in:

codex plugin marketplace add alis-build/codex-plugin && codex plugin add tools@alis-build && codex mcp login alis-build && codex

The sign-in flow opens https://identity.alisx.com in your browser.

Sign In

In Codex, run:

/mcp

You should see alis-build listed as an MCP server.

Use It

After sign-in, ask Codex 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.

Codex will use the Alis Build tools without asking for approval on every MCP call.

Workflow Skills

This plugin includes Alis Build workflow skills:

build it
fix it
Use the Alis Build - Getting Started skill to help me get started on Alis Build.

build it discovers the right Alis Build skill for the thing you want to build. fix it is an alias for the same discovery flow when the goal is framed as a fix.

Workspace Context

This plugin ships Codex hooks that keep sessions grounded in the Alis Build workflow:

• Standing DBD primer + routing. A SessionStart hook loads the Define → Build → Deploy primer into every session (so Codex frames help around the platform lifecycle), together with the routing contract: build/fix → discover the right skill via SearchSkills first instead of editing code directly; define it / deploy it → run the alis CLI; spec it → call SpecIt directly. It is always present, so no trigger word is needed and follow-up requests stay grounded. Works in any directory, not just an Alis Build workspace.
• Service context (workspace-aware). A SessionStart hook detects when the session is opened inside an Alis Build service folder (~/alis.build/<org>/build|define/…) and injects the package id plus a pointer to the matching definitions ⇄ implementation counterpart. Silent outside a workspace.
• Session-aware skills. When Codex loads an Alis Build skill, the plugin enriches the request with the active session so the server can return runtime context for your current workspace.
• alis CLI access. A SessionStart hook ensures Codex can run the alis CLI without per-command approval prompts. alis subcommands need network access and your local session, which Codex's sandbox blocks; the only lever that runs a command unrestricted is an execpolicy allow rule, and a plugin manifest cannot declare one. So the hook writes a dedicated ~/.codex/rules/alis-build.rules containing prefix_rule(pattern=["alis"], decision="allow") if no rule already grants it. It takes effect from the next session if Codex loads rules before the hook runs. To remove it, delete that file (and the ["alis"] entry from ~/.codex/rules/default.rules if you also approved it interactively). Production deploys stay safe despite the broad allow: the CLI itself refuses to deploy to a production environment (exit code 3) until re-run with --confirm-production, which the agent is instructed to add only after your explicit approval (alis docs safety).

Hooks are enabled by default in Codex. If you have disabled them globally, re-enable them by removing [features].hooks = false from ~/.codex/config.toml.

Troubleshooting

If alis-build does not appear in /mcp, confirm that the plugin install completed successfully:

codex plugin add tools@alis-build

If sign-in fails, confirm that you can reach both https://mcp.alis.build and https://identity.alisx.com, then run the login command again:

codex mcp login alis-build

If you see Dynamic client registration not supported, remove any manually added MCP server with the same name and use the plugin-provided configuration:

codex mcp remove alis-build
codex mcp login alis-build

That error usually means alis-build was previously added with codex mcp add alis-build --url https://mcp.alis.build, which does not include the Alis Build OAuth client ID.