Command line

Adios for Codex CLI.

Connect Codex directly to the hosted Adios endpoint for source-backed development, previews, logs, and approved deployments.

Install now Client docs

Connection: Remote HTTP
Authentication: OAuth
Access: Read, write, and approval-gated deploy

Setup

Install.

Codex connects directly to the hosted Adios MCP endpoint. No local proxy or platform token is required.

01
Add Adios
Register the hosted Adios endpoint under the name adios.
Command
```
codex mcp add adios --url https://api.adios.dev/v1/mcp
```
02
Authenticate
Start the OAuth flow and authorize the correct Adios user and team.
Command
```
codex mcp login adios
```

Try a prompt

Start a Codex session, confirm the connection, or jump into a real build.

Prompt 1

Use Adios MCP to confirm my user and team with auth_me.

Prompt 2

Build me a Next.js landing page and give me a working preview URL.

Prompt 3

Open this repository, fix the failed build, and show me the healthy preview URL.

Tool access

Capabilities.

The client uses the same scoped Adios tool surface. The live discovery endpoint remains the source of truth for schemas.

Workspaces

List, inspect, create, and prepare source-backed Adios workspaces.

list_workspacesget_workspacecreate_workspace

Source

Read and update project files while keeping changes visible in the workspace and Git state.

read_workspace_filewrite_workspace_fileget_workspace_git_status

Builds

Run lint and build commands, start a preview, and follow long-running command state.

lint_workspacebuild_workspace_devstart_workspace_run

Logs

Read command, build, preview, and production logs to diagnose real failures.

get_workspace_command_logsget_workspace_logsget_workload_logs

Deployment

Review the workspace and deploy only after the user explicitly approves the operation.

security_review_workspacedeploy_workspacedeploy_workload

View every MCP function

Full workflow

Build and verify.

“Can you add a pricing page to this Next.js app with monthly and yearly billing, a plan comparison table, and an FAQ? Match the existing design, make sure it works on mobile, and send me a preview link.”

01
Inspect
Open the Adios workspace, inspect its files, and identify the project commands.
create_workspacelist_workspace_filesread_workspace_file
02
Configure
Create or validate adios.yaml before running project commands.
write_workspace_adios_yamlcheck_workspace_adios_yaml
03
Fix and build
Run lint, make the smallest necessary source changes, and build the project.
lint_workspacewrite_workspace_filebuild_workspace_dev
04
Run and verify
Start the preview, inspect its logs and health, then return the verified URL.
start_workspace_runget_workspace_command_logsget_workspace_run_status

Help

FAQ.

Does Codex CLI need the Adios plugin?

No. The two codex mcp commands connect the hosted server directly. The plugin is optional and adds reusable Adios workflow skills.

Where does Codex store the connection?

Codex manages the MCP connection in its own configuration. Keep Adios OAuth credentials out of project source and let the client manage the OAuth session.

How do I verify the connection?

Ask Codex to call auth_me. A successful response should identify the authorized Adios principal and current team context.

Can this client deploy to production?

Yes. Deployment tools are available, but deployment and other sensitive operations remain approval-gated. The client should explain the intended action and wait for explicit confirmation.

Catalog