Workspaces
List, inspect, create, and prepare source-backed Adios workspaces.
list_workspacesget_workspacecreate_workspaceCompatibility bridge
Use the public npm bridge when your MCP client can launch a local command but cannot connect to remote HTTP directly.
Setup
The npm package runs a small local transport bridge. Adios tools, workspaces, builds, and workloads remain hosted.
Install Node.js 20 or newer on the machine running your MCP client.
node --versionCreate an MCP server named adios using this command in your client's configuration.
npx -y @adiosdotdev/mcpRestart or reload the client so it launches the bridge and discovers the Adios tools.
Complete the browser OAuth flow when the bridge connects to Adios.
Open a new session, confirm the connection, or jump into a real build.
Use Adios MCP to confirm my user and team with auth_me.Build me a Next.js landing page and give me a working preview URL.Open this repository, fix the failed build, and show me the healthy preview URL.Tool access
The client uses the same scoped Adios tool surface. The live discovery endpoint remains the source of truth for schemas.
List, inspect, create, and prepare source-backed Adios workspaces.
list_workspacesget_workspacecreate_workspaceRead and update project files while keeping changes visible in the workspace and Git state.
read_workspace_filewrite_workspace_fileget_workspace_git_statusRun lint and build commands, start a preview, and follow long-running command state.
lint_workspacebuild_workspace_devstart_workspace_runRead command, build, preview, and production logs to diagnose real failures.
get_workspace_command_logsget_workspace_logsget_workload_logsReview the workspace and deploy only after the user explicitly approves the operation.
security_review_workspacedeploy_workspacedeploy_workloadFull workflow
“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.”
Open the Adios workspace, inspect its files, and identify the project commands.
create_workspacelist_workspace_filesread_workspace_fileCreate or validate adios.yaml before running project commands.
write_workspace_adios_yamlcheck_workspace_adios_yamlRun lint, make the smallest necessary source changes, and build the project.
lint_workspacewrite_workspace_filebuild_workspace_devStart the preview, inspect its logs and health, then return the verified URL.
start_workspace_runget_workspace_command_logsget_workspace_run_statusHelp
Only the stdio-to-remote transport bridge. Adios workspaces, builds, previews, tools, and production workloads remain hosted by Adios.
The @adiosdotdev/mcp package requires Node.js 20 or newer.
No static token is required. Let the bridge open the Adios OAuth flow and authorize the intended user and team.
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
Command line
Connect Codex directly to the hosted Adios endpoint for source-backed development, previews, logs, and approved deployments.
View setupWeb and desktop
Install one Adios plugin with the hosted MCP connection plus guided build, deploy, operate, and debug workflows.
View setupWeb and desktop
Add Adios as a custom connector in Claude or Claude Desktop, then build, preview, debug, and deploy from a conversation.
View setupCommand line
Connect Claude Code to Adios from the terminal and use hosted workspace, preview, log, and deployment tools beside your repository.
View setupConnect stdio MCP clients, authorize your team, and move from source to a healthy preview before any production change.
Create an Adios account