Adios
All MCP clients

Compatibility bridge

Adios for stdio MCP clients.

Use the public npm bridge when your MCP client can launch a local command but cannot connect to remote HTTP directly.

Connection
Local stdio bridge
Authentication
Browser OAuth
Access
Read, write, and approval-gated deploy

Setup

Install.

The npm package runs a small local transport bridge. Adios tools, workspaces, builds, and workloads remain hosted.

  1. 01

    Check Node.js

    Install Node.js 20 or newer on the machine running your MCP client.

    Command
    node --version
  2. 02

    Add the command

    Create an MCP server named adios using this command in your client's configuration.

    Command
    npx -y @adiosdotdev/mcp
  3. 03

    Start the client

    Restart or reload the client so it launches the bridge and discovers the Adios tools.

  4. 04

    Authorize

    Complete the browser OAuth flow when the bridge connects to Adios.

  5. 05

    Try a prompt

    Open a new 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.
  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.

What runs locally?

Only the stdio-to-remote transport bridge. Adios workspaces, builds, previews, tools, and production workloads remain hosted by Adios.

Which Node.js version is required?

The @adiosdotdev/mcp package requires Node.js 20 or newer.

Can I use a static Adios token?

No static token is required. Let the bridge open the Adios OAuth flow and authorize the intended user and team.

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 stdio MCP clients, authorize your team, and move from source to a healthy preview before any production change.

Create an Adios account