Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.
MCPpedia last refreshed this data
io.github.bea-technology/roxyon is an MCP server that build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure. Its tool list has not been published yet over stdio and http, requires no API key, and scores 86/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"roxyon": {
"args": [
"-y",
"@roxyon/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Build LumenJS apps, use the Roxyon BaaS, and deploy apps and web projects to Roxyon infrastructure.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y '@roxyon/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @roxyon/mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in devops
MCP server for using the GitLab API
MCP server for discovering, reading, and changing ZenML resources with compact generic tools
MCP server for Dynatrace Managed to access logs, events, and metrics.
An MCP server for Azure DevOps
MCP Security Weekly
Get CVE alerts and security updates for io.github.bea-technology/roxyon and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
| Package | What it is | Status |
|---|---|---|
@roxyon/api-client | Typed client for the Roxyon BaaS (RX engine) + the Applications/Sites deploy endpoints | M1 |
@roxyon/deploy-core | Shared deploy pipeline — project detection, archiving, build/upload/poll orchestration | M1 |
@roxyon/cli | roxyon — login, init, deploy, logs, env, restart, open, link | M1 |
@roxyon/mcp | MCP server — stdio (roxyon-mcp) for local clients, remote Streamable HTTP + OAuth (roxyon-mcp-http) for hosted connectors | M2 |
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 checklist | M3 — drafted |
create-roxyon-app | npm create roxyon-app — LumenJS / Node templates, emits AGENTS.md + roxyon.json + llms.txt + editor rules | M4 |
integrations/ | Per-assistant wrappers — Claude Code plugin, ChatGPT GPT, Cursor/etc. install snippets | M5 |
See docs/roadmap.md for the full plan.
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
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.
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.
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.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