Command line

Adios for Grok.

Connect Grok CLI to the hosted Adios endpoint for workspace source, builds, previews, logs, and approved deployments.

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

Setup

Install.

Run one command. Grok registers Adios as a hosted HTTP server, discovers OAuth automatically, and opens the browser when you first use an Adios tool.

01
Add Adios
Run this once. http means the server is hosted, adios is its local name, and the final value is the public endpoint. Do not add -- or an Authorization header.
Command
```
grok mcp add --transport http adios https://api.adios.dev/v1/mcp
```
02
Check it
Confirm Grok saved the server before opening a session.
Command
```
grok mcp list
```
03
Sign in
Start Grok and use an Adios tool. OAuth opens automatically. You can also open /mcps, select Adios, and press i to start sign-in yourself.
Command
```
/mcps
```
04
Check errors
If Adios does not connect, ask Grok to test its configuration and HTTP connection.
Command
```
grok mcp doctor adios
```

Try a prompt

Ask Grok to verify the connection or work on a real Adios 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.”

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.

Why is there no -- or --header?

Everything after -- is a command for a local stdio server. --header sends a static credential to a remote server. Adios is remote and uses OAuth, so neither belongs in its command.

Can I keep it in the project?

Yes. Add --scope project to the add command. Grok writes the connection to .grok/config.toml in the current repository instead of your user config.

Can I edit TOML instead?

Yes. Add an mcp_servers.adios table with url set to the Adios endpoint in ~/.grok/config.toml or .grok/config.toml. The CLI command is quicker and avoids formatting mistakes.

Where are Grok's OAuth tokens stored?

Grok stores them in ~/.grok/mcp_credentials.json, outside your project configuration. Do not commit that credentials file.

Can I use Grok on the web?

Grok's web product accepts public custom MCP connectors too. This guide uses Grok CLI because its setup and troubleshooting commands are repeatable.

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