Adios
All MCP clients

Editor companion

Adios for Sublime Text.

Use the Adios Sublime Text extension for workspace actions and an MCP-capable companion for conversational Adios tools in the same project.

Connection
Extension and MCP companion
Authentication
OAuth through the CLI or companion
Access
Read, write, and approval-gated deploy

Setup

Install.

The Adios extension is built and will be published to Package Control soon. It handles direct workspace actions. For MCP conversations today, run Codex, Claude Code, or OpenCode beside Sublime Text.

  1. 01

    Install the CLI

    The Sublime extension delegates account and workspace operations to the Adios CLI.

    Command
    brew install adiosdotdev/tap/adios
  2. 02

    Watch for release

    The extension is not in Package Control yet. Once published, install Adios from Package Control and use its command palette or sidebar actions.

  3. 03

    Open the project

    Open your repository in Sublime Text, then open a terminal at the same project root for your MCP companion.

  4. 04

    Connect MCP

    Connect your preferred companion agent. This example uses Codex CLI.

    Command
    codex mcp add adios --url https://api.adios.dev/v1/mcp
    codex mcp login adios
  5. 05

    Start the agent

    Run the companion from the project root so its file changes stay visible in Sublime Text.

    Command
    codex
  6. 06

    Try a prompt

    Ask the companion to use Adios while you review the same files in Sublime Text.

    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.
  1. 01

    Inspect

    Open the Adios workspace, inspect its files, and identify the project commands.

    create_workspacelist_workspace_filesread_workspace_file
  2. 02

    Configure

    Create or validate adios.yaml before running project commands.

    write_workspace_adios_yamlcheck_workspace_adios_yaml
  3. 03

    Fix and build

    Run lint, make the smallest necessary source changes, and build the project.

    lint_workspacewrite_workspace_filebuild_workspace_dev
  4. 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.

Can I install the extension now?

Not from Package Control yet. The extension is built and in release testing. This guide will link to its Package Control page as soon as it is published.

What does the extension add?

It adds Adios login, team and workspace selection, reviewed sync, preview, command output, and confirmed production deployment through Sublime Text commands and sidebar actions.

Does the extension replace MCP?

No. The extension runs focused platform actions through the Adios CLI. The companion agent supplies the conversational MCP experience and edits the same local files.

Will edits appear in Sublime Text?

Yes. The companion edits the same local repository, and Sublime Text detects the changed files for review.

How do I verify the connection?

Ask the client to call auth_me. A successful response identifies the authorized Adios user and current team context.

How do I disconnect it?

Open Marketplace in the Adios app, find AI clients, and choose Disconnect. Adios revokes that user's grant and refresh-token family without affecting anyone else.

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.

Start with Adios.

Connect Sublime Text, authorize your team, and move from source to a healthy preview before any production change.

Create an Adios account