AASC / INTEGRATIONS / MCP
Your local Codex. A shared control room.
Use Codex on your computer to inspect runners and operate the same jobs you see in the console.
One service, two ways to operate.
The console and AASC Operations MCP share persistent jobs, permissions and audit history. Local Codex is the client; an authorized runner does the project work.
CODEX → AASC MCP → JOBS → RUNNER
“Preview a repository-report batch for these projects, run two at a time, then show me the results.”
Set up the self-hosted service
- Install and initialize the operations package from this website checkout.
- Start the control service and a registered runner.
- Use the separate Codex token from the generated private configuration.
source .aasc/codex.env
codex mcp add aasc-ops \
--url http://127.0.0.1:4318/mcp \
--bearer-token-env-var AASC_OPS_TOKENRun after initializing the companion service. This command connects to your own running service, not a hosted AASC endpoint.
Vultr: inspect first, approve specific changes.
Official Vultr MCP
Provides read-only infrastructure inspection. Connect it separately using Vultr’s official OAuth setup.
Official setup ↗AASC Operations
Prepare exact-machine start, halt or reboot plans. A separately authorized person approves the plan before the API adapter applies it. Provider credentials stay on the backend.
Provider connection and live cloud operations require operator setup. Provisioning and deletion are not enabled.
START WITH ONE MACHINE