Enables AI assistants to build LumenJS applications, utilize Roxyon BaaS, and deploy web projects to Roxyon infrastructure.
Also known as bea-technology/roxyon-devtools, @roxyon/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.7.0
- Last commit
- Nov 2, 2026
- License
- MIT
What is Roxyon MCP?
Roxyon enables AI assistants to build LumenJS applications, utilize Roxyon BaaS, and deploy web projects to Roxyon infrastructure.
Summary generated from the project's README
About Roxyon MCP server
Building LumenJS applications and managing web deployments through an AI assistant is what this server enables. Developers can use it to create apps, interact with Roxyon Backend as a Service, and push web projects directly to Roxyon infrastructure. It operates via stdio and integrates with clients like Claude Code, Cursor, Windsurf, Cline, and the Gemini CLI.
To use the server, you must authenticate using the Roxyon CLI or by providing a ROXYON_TOKEN in your environment variables. The server provides specific tools such as roxyon_init for project setup, roxyon_deploy for publishing, and roxyon_logs for monitoring. It also offers resources like roxyon://docs/lumenjs to provide the assistant with technical documentation. For security, any tool that causes side effects requires a confirm:true parameter to execute.
What you can do with it
- 1Scaffold a new applicationAsk the AI to generate a new LumenJS project structure using the built-in prompts.
- 2Deploy a web projectInstruct the assistant to build and upload your application to the Roxyon infrastructure.
Written from the project's README. Every use case is checked against a quote from it.
How to install Roxyon MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Roxyon MCP in Claude Code
$ claude mcp add --env 'ROXYON_TOKEN=<YOUR_ROXYON_TOKEN>' roxyon -- npx -y @roxyon/mcpInstall Roxyon MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"roxyon": {
"command": "npx",
"args": [
"-y",
"@roxyon/mcp"
],
"env": {
"ROXYON_TOKEN": "<YOUR_ROXYON_TOKEN>"
}
}
}
}Install Roxyon MCP in VS Code
.vscode/mcp.json
{
"servers": {
"roxyon": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@roxyon/mcp"
],
"env": {
"ROXYON_TOKEN": "<YOUR_ROXYON_TOKEN>"
}
}
}
}Install Roxyon MCP in VS Code CLI
$ code --add-mcp '{"name":"roxyon","type":"stdio","command":"npx","args":["-y","@roxyon/mcp"],"env":{"ROXYON_TOKEN":"<YOUR_ROXYON_TOKEN>"}}'Install Roxyon MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"roxyon": {
"command": "npx",
"args": [
"-y",
"@roxyon/mcp"
],
"env": {
"ROXYON_TOKEN": "<YOUR_ROXYON_TOKEN>"
}
}
}
}Install Roxyon MCP in Codex
$ codex mcp add roxyon --env 'ROXYON_TOKEN=<YOUR_ROXYON_TOKEN>' -- npx -y @roxyon/mcpInstall Roxyon MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.roxyon] command = "npx" args = ["-y", "@roxyon/mcp"] [mcp_servers.roxyon.env] ROXYON_TOKEN = "<YOUR_ROXYON_TOKEN>"
Install Roxyon MCP in Gemini CLI
$ gemini mcp add -s user -e 'ROXYON_TOKEN=<YOUR_ROXYON_TOKEN>' roxyon npx -- -y @roxyon/mcpInstall Roxyon MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"roxyon": {
"command": "npx",
"args": [
"-y",
"@roxyon/mcp"
],
"env": {
"ROXYON_TOKEN": "<YOUR_ROXYON_TOKEN>"
}
}
}
}Configuration
ROXYON_TOKENSecretA roxp_ personal access token (alternative to `roxyon login`). Create one with `roxyon token create`.
ROXYON_API_URLOverride the BaaS base URL (default https://www.beaapis.com/1).
ROXYON_CONSOLE_URLOverride the console base URL (default https://console.roxyon.com).
| Name | Description | |
|---|---|---|
| ROXYON_TOKEN | A roxp_ personal access token (alternative to `roxyon login`). Create one with `roxyon token create`. | Secret |
| 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). |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablebea-technology/roxyon-devtools is public and reachablegithub.com/bea-technology/roxyon-devtools ↗Pass
- Package names this repository as its source@roxyon/mcp names bea-technology/roxyon-devtools as sourcenpmjs.com/package/@roxyon/mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @roxyon/mcpnpmjs.com/package/@roxyon/mcp/v/0.7.0#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-02github.com/bea-technology/roxyon-devtools ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @roxyon/mcpPass
- No critical advisory in the package or its dependencies108 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHub@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
- The assistant reads
roxyon://docs/lumenjs+roxyon://docs/baas, writes the app. roxyon_init { dir }→ writesroxyon.json.roxyon_deploy { dir }→ dry-run plan.roxyon_deploy { dir, confirm: true }→ builds, uploads, waits for it to go live (app runtimes) and reports the URL or the failure reason.
Roxyon MCP questions
How do I add Roxyon MCP to Claude Code?
Run claude mcp add --env 'ROXYON_TOKEN=<YOUR_ROXYON_TOKEN>' roxyon -- npx -y @roxyon/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Roxyon MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.