io.github.bea-technology/roxyon

Official registry Cloud and DevOps

Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http roxyon 'https://mcp.roxyon.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "roxyon": {
            "type": "http",
            "url": "https://mcp.roxyon.com/mcp"
        }
    }
}
NPM package @roxyon/mcp
Claude Code
claude mcp add roxyon -e 'ROXYON_TOKEN=<your roxyon_token>' -e 'ROXYON_API_URL=<ROXYON_API_URL>' -e 'ROXYON_CONSOLE_URL=<ROXYON_CONSOLE_URL>' -- npx -y @roxyon/mcp@0.7.0
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "roxyon": {
            "command": "npx",
            "args": [
                "-y",
                "@roxyon/mcp@0.7.0"
            ],
            "env": {
                "ROXYON_TOKEN": "<your roxyon_token>",
                "ROXYON_API_URL": "<ROXYON_API_URL>",
                "ROXYON_CONSOLE_URL": "<ROXYON_CONSOLE_URL>"
            }
        }
    }
}

Environment variables

  • ROXYON_TOKEN secret A roxp_ personal access token (alternative to `roxyon login`). Create one with `roxyon token create`.
  • ROXYON_API_URL Override the BaaS base URL (default https://www.beaapis.com/1).
  • ROXYON_CONSOLE_URL Override the console base URL (default https://console.roxyon.com).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. roxyon-devtools
  2. Quick start
  3. Develop
  4. How deploy works

roxyon-devtools

Tooling that lets a developer — or an AI assistant acting for one — build with LumenJS, use the Roxyon BaaS, and deploy to Roxyon infrastructure from anywhere.

PackageWhat it isStatus
@roxyon/api-clientTyped client for the Roxyon BaaS (RX engine) + the Applications/Sites deploy endpointsM1
@roxyon/deploy-coreShared deploy pipeline — project detection, archiving, build/upload/poll orchestrationM1
@roxyon/cliroxyon — login, init, deploy, logs, env, restart, open, linkM1
@roxyon/mcpMCP server — stdio (roxyon-mcp) for local clients, remote Streamable HTTP + OAuth (roxyon-mcp-http) for hosted connectorsM2
backend/The two new console endpoints + node script (/applications/deploy, /sites/deploy, app-source-apply.sh)written & wired in _configs, not synced
docs/llms.txt, BaaS OpenAPI 3.1, AGENTS.md template, distribution checklistM3 — drafted
create-roxyon-appnpm create roxyon-app — LumenJS / Node templates, emits AGENTS.md + roxyon.json + llms.txt + editor rulesM4
integrations/Per-assistant wrappers — Claude Code plugin, ChatGPT GPT, Cursor/etc. install snippetsM5

See docs/roadmap.md for the full plan.

Quick start

npm create roxyon-app@latest my-app     # LumenJS or Node, wired for deploy
cd my-app
npm i -g @roxyon/cli && roxyon login
roxyon deploy                            # builds + uploads + waits for it to go live

Existing project instead of a new one: roxyon init writes roxyon.json, then roxyon deploy.

CI (no interactive login) — create a token once, then use it as ROXYON_TOKEN:

roxyon token create ci --scopes deploy,logs      # prints roxp_… once
ROXYON_TOKEN=roxp_xxx roxyon deploy --no-follow   # first run also creates the app
From an AI assistant

Local clients (Claude Code, Cursor, Windsurf, Cline, Gemini CLI) — add the stdio server:

{ "mcpServers": { "roxyon": { "command": "npx", "args": ["-y", "@roxyon/mcp"] } } }

then the assistant calls roxyon_init and roxyon_deploy.

Claude Code plugin — bundles the server + /roxyon-deploy and /roxyon-new slash commands + a skill:

/plugin marketplace add bea-technology/roxyon-devtools
/plugin install roxyon

Remote connectors (claude.ai, ChatGPT, Cursor URL) — connect to https://mcp.roxyon.com/mcp and sign in with your Roxyon account (OAuth, no token to paste). roxyon_init / roxyon_deploy are local-only there; use roxyon_link_github for push-to-deploy.

Add to Cursor:

See packages/mcp-server and integrations/mcp-clients.md.

Develop

corepack enable pnpm
pnpm install
pnpm build        # all packages
pnpm test
pnpm typecheck
pnpm lint

Node ≥ 20. The repo is a pnpm workspace; tsup builds each package, vitest tests, biome lints + formats, changesets versions releases.

How deploy works

  • LumenJS / static (runtime: "lumen", kind: "static"): roxyon deploy runs lm build --serverless, tars dist/, and POSTs it to /sites/deploy, which extracts it into the host's document root. Served directly by nginx.
  • Node / Python / PHP (kind: "app"): the tarball goes to /applications/deploy, which lands it in the application's SourcePath and bumps ConfigRevision. The existing reconciler builds it in an isolated release dir and runs it under a systemd unit. Git remotes connected with roxyon link auto-deploy on push via the existing webhook.

Authentication is a Roxyon session token today (stored 0600 in ~/.roxyon/config.json); scoped Personal Access Tokens land in M1.5.

Frequently asked questions

What is io.github.bea-technology/roxyon?

Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

How do I install io.github.bea-technology/roxyon?

It runs as a remote server. In Claude Code: claude mcp add --transport http roxyon 'https://mcp.roxyon.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.bea-technology/roxyon need an API key?

Yes. It expects ROXYON_TOKEN, which you set in its configuration.

Is io.github.bea-technology/roxyon open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.bea-technology/roxyon?

It is published by bea-technology. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.