FAQ

Common questions and answers that come up while using AxHub.

This page collects only short questions and answers. If you have a symptom and need to narrow down the cause, Troubleshooting is faster.

Did the CLI install address change?

Yes. The current domain for the public install script is https://cli.axhub.ai.

curl -fsSL https://cli.axhub.ai/install.sh | bash

After installing, global options and output formats are covered in the CLI reference.

Where are the MCP tools?

On the AxHub MCP server (https://mcp.axhub.ai/mcp). Connect an MCP client like Claude Code and you get 20 read-oriented default tools — app and deploy lookups, app DB and connector reads, SDK knowledge search, and more. If the server's deploy-write gate is on, 21 operational-change tools such as app creation and deploy triggering are added, for 41 in total. The connection steps are in Connecting AI tools.

Which deploy methods are supported?

The deploy method is determined in this order: axhub.yaml (manifest) → Dockerfile → Compose file → Railpack auto-detection. An app's deploy_method is one of docker | compose | static and cannot be changed after the app is created — if the manifest's value differs from the value recorded on the app, the deploy fails. The full schema is in the axhub.yaml reference.

How does my app read the signed-in user?

Read the X-AxHub-* headers that the gate in front of your app forwards, on the server. email/name are base64-encoded. Per-language examples are in Read the SSO user info.

When do I use a PAT vs OAuth?

Use a PAT (AXHUB_API_KEY) on the surfaces where it's allowed, such as SDK calls and CI. For app creation, deploys, GitHub connection, and tenant / member / admin work, use OAuth device login (device flow). The login commands are in CLI — Auth.