gxmesh CLI reference
Every gxmesh CLI command for deploying MCP servers on Glxymesh: login, org and project scope, new, push, tools, rm, update, completion and env vars.
Install
Section titled “Install”curl -fsSL https://platform.glxymesh.com/install.sh | bash # macOS, Linuxirm https://platform.glxymesh.com/install.ps1 | iex # Windows PowerShellFor Windows cmd, see the quickstart.
Account
Section titled “Account”| Command | What it does |
|---|---|
gxmesh login |
Signs this machine in with the device flow. The CLI shows a URL and a code to enter in any browser. |
gxmesh auth list |
Shows this account and every session it has open. |
gxmesh services |
Shows the account’s tier and capabilities. |
gxmesh logout |
Removes stored credentials. |
gxmesh auth login and gxmesh auth logout are the same as the short forms.
push, tools and rm act on the active organization and project.
| Command | What it does |
|---|---|
gxmesh org |
Lists your organizations. |
gxmesh org use [slug] |
Makes an organization active. With no slug, it lets you pick one. |
gxmesh project |
Lists the projects in the active organization. |
gxmesh project use [slug] |
Makes a project active. With no slug, it lets you pick one. |
gxmesh project create <slug> [name] |
Creates a project, with an optional display name. |
gxmesh project describe <slug> <description> |
Sets the project description. It seeds the MCP instructions that tell a connected model what this server is for. |
If you haven’t chosen a project, default is used. It’s created the first time you use it.
You can override the scope for a single command with --org <slug> and --project <slug>, or with the
GXMESH_ORG and GXMESH_PROJECT environment variables. A stored project applies only to its own
organization, so passing --org alone doesn’t carry it over.
| Command | What it does |
|---|---|
gxmesh new <name> [--lang go] |
Scaffolds a tool in a new directory <name>. It won’t write into a directory that isn’t empty. |
gxmesh push [manifest.json] |
Publishes the tool in the current directory. If a matching .wasm is next to the manifest, it’s uploaded as is. Otherwise the platform compiles the .go files. See dependencies. |
gxmesh tools |
Lists the tools in the active project. |
gxmesh rm <name> |
Removes a tool from the active project. |
The CLI itself
Section titled “The CLI itself”| Command | What it does |
|---|---|
gxmesh version |
Shows this binary’s version and the services it talks to. |
gxmesh update [--force] |
Replaces the binary with the current release. --force reinstalls even if the version matches. The CLI also tells you, at most once a day, when a newer release exists. |
gxmesh completion <bash|zsh|fish> |
Prints a shell completion script. |
To enable tab completion:
source <(gxmesh completion bash) # add to ~/.bashrcsource <(gxmesh completion zsh) # add to ~/.zshrcgxmesh completion fish | source # add to ~/.config/fish/config.fishEnvironment variables
Section titled “Environment variables”| Variable | Effect |
|---|---|
GXMESH_ORG, GXMESH_PROJECT |
Override the active organization and project. |
GXMESH_PLAIN=1 |
Turns off colour and all terminal drawing. |
NO_COLOR |
Turns off colour. |
GXMESH_THEME=light|dark |
Sets the terminal background instead of detecting it. |
Credentials and the active scope are stored in ~/.config/gxmesh.