Roxyon

io.github.bea-technologyPublished by GitHub account bea-technologyv0.7.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

Roxyon's MCP server lets an assistant build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

What you can do
Read bundled LumenJS, BaaS and deploy documentation resources and use scaffold and deploy prompts to start a project. Check the signed-in account, list domains and apps, and initialize a project directory with a Roxyon config file. Deploy a directory with a dry-run plan first, then a confirmed build and upload that waits for the app to go live and reports the URL or failure. Inspect app status and logs, restart an app, read and set environment variables, and link a GitHub repository.
When to use it
Useful when you are building LumenJS applications or web projects on the Roxyon backend-as-a-service and want the assistant to scaffold, configure, deploy and operate them from the same conversation.
Requirements
Runs locally over stdio via npx from the npm package, or as a remote endpoint. Authentication is required: either a stored login from the Roxyon CLI or a personal access token in ROXYON_TOKEN. ROXYON_API_URL and ROXYON_CONSOLE_URL optionally override the default base URLs. Network access to Roxyon services is needed.
Before you install
The token in ROXYON_TOKEN is a credential granting access to your Roxyon account; keep it out of shared configs. Deploy, restart, environment-variable changes and GitHub linking change remote state, though side-effecting tools require confirm:true and deploy defaults to a dry run. Environment variables set through the server may include secrets. Deployed code and project files are uploaded to Roxyon infrastructure.

Installation

In SourceWeft

  1. Open Roxyon in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.bea-technology%2Froxyon/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "roxyon": {
      "type": "http",
      "url": "https://mcp.roxyon.com/mcp"
    }
  }
}

README

@roxyon/mcp

Model Context Protocol server for Roxyon. Gives any MCP-capable AI assistant the ability to build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.

Runs on stdio. A remote Streamable-HTTP transport with OAuth is planned (needs the M1.5 Personal Access Token work).

Install

bash
npm i -g @roxyon/mcp    # or use npx, below

Authenticate once with the CLI (the MCP server reuses its stored login):

bash
npm i -g @roxyon/cliroxyon login

…or set ROXYON_TOKEN in the server's environment (CI / headless).

Add it to a client

Claude Code — .mcp.json in a project, or claude mcp add:

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

Cursor / Windsurf / Cline — same shape in their MCP settings.

Gemini CLI — ~/.gemini/settings.json → mcpServers → same shape.

Pass through ROXYON_TOKEN (and optionally ROXYON_API_URL, ROXYON_CONSOLE_URL) via the client's env field when not using a stored login.

What it exposes

Tools — roxyon_whoami, roxyon_list_domains, roxyon_list_apps, roxyon_init, roxyon_deploy (dry-run unless confirm:true), roxyon_app_status, roxyon_logs, roxyon_restart, roxyon_env_get, roxyon_env_set, roxyon_link_github. Every side-effecting tool requires confirm:true.

Resources — roxyon://docs/lumenjs (the full LumenJS V1 reference), roxyon://docs/baas, roxyon://docs/deploy.

Prompts — scaffold-lumen-app, deploy-to-roxyon.

Typical flow

  1. The assistant reads roxyon://docs/lumenjs + roxyon://docs/baas, writes the app.
  2. roxyon_init { dir } → writes roxyon.json.
  3. roxyon_deploy { dir } → dry-run plan.
  4. roxyon_deploy { dir, confirm: true } → builds, uploads, waits for it to go live (app runtimes) and reports the URL or the failure reason.

Source: packages/mcp-server/README.md at commit 191465f

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v0.7.0LatestOct 18, 2026
  2. v0.4.0Oct 2, 2026
  3. v0.3.0Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts