Adios
All MCP clients

Code editor

Adios for VS Code.

Use VS Code's built-in MCP support for Adios tools today. The separate Adios extension adds a sidebar for workspace sync, previews, and deployments.

Install nowClient docs
Connection
Remote HTTP
Authentication
OAuth with dynamic registration
Access
Read, write, and approval-gated deploy

Setup

Install.

Add Adios to VS Code's built-in MCP configuration. VS Code starts the server, asks you to trust it, and opens Adios OAuth when a tool first needs your account.

  1. 01

    Choose a scope

    Run MCP: Open User Configuration to use Adios in every project. For one repository, create .vscode/mcp.json instead.

  2. 02

    Paste the config

    Add the remote HTTP entry shown in Client config, then save the file. It contains no secret or static API token.

  3. 03

    Start Adios

    Use the inline Start action in mcp.json, or run MCP: List Servers and select Adios. Confirm trust, then finish sign-in in the browser.

  4. 04

    Check tools

    Open Chat and select Configure Tools. Expand Adios to confirm its tools are available and choose which ones the agent may use.

  5. 05

    Try a prompt

    Open agent mode and ask VS Code to verify Adios or build a project.

    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.

Do I need the Adios extension?

No. VS Code's built-in MCP support works with the mcp.json entry above. The Adios extension is a separate convenience layer for sync, preview, and deploy actions in the editor sidebar.

When will the extension be in the Marketplace?

The extension is packaged and going through release checks. It will be published under the adiosdotdev publisher, and this page will link to it once the listing is live.

How is the extension published?

A tested VSIX is published under the adiosdotdev publisher with Microsoft's vsce workflow. That Marketplace release is separate from the built-in MCP connection, which is available now.

Do I add an OAuth client ID?

No. Leave the oauth block out so VS Code uses Adios dynamic client registration and opens the browser on first use.

Should the config be global or project-scoped?

Use the user configuration when you want Adios everywhere. Use .vscode/mcp.json when the connection should travel with one workspace.

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.

Catalog

Other clients.

View catalog →

Command line

Codex CLI

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

View setup

Web and desktop

ChatGPT

Install one Adios plugin with the hosted MCP connection plus guided build, deploy, operate, and debug workflows.

View setup

Web and desktop

Claude

Add Adios as a custom connector in Claude or Claude Desktop, then build, preview, debug, and deploy from a conversation.

View setup

Command line

Claude Code

Connect Claude Code to Adios from the terminal and use hosted workspace, preview, log, and deployment tools beside your repository.

View setup

Start with Adios.

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

Create an Adios account