mcpField
R
roxyon

roxyon

Remote
github.com/bea-technologyDeveloper Tools0Updated 2w ago
Repository

About roxyon

roxyon is an MCP server for AI assistants building LumenJS apps, using Roxyon BaaS, and deploying projects to Roxyon infrastructure. It exposes deployment and app-management operations alongside documentation and prompts.

Key features

  1. 01Initialize LumenJS projects
  2. 02Deploy apps with dry-run support
  3. 03Inspect app status and logs
  4. 04Manage environment variables
  5. 05Access LumenJS, BaaS, and deployment docs

Use cases

  1. 01Scaffold a LumenJS app
  2. 02Preview a deployment before confirmation
  3. 03Check an app's status or logs

MCP support

Runs over stdio and exposes Roxyon tools, documentation resources, and prompts to MCP clients. Side-effecting tools require `confirm:true`.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.roxyon.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Packages
npm@roxyon/mcp0.7.0

Tools

Details

From the project 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

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

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

npm i -g @roxyon/cli
roxyon 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:

{
  "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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.