@tenkicloud/mcp 0.4.0 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,6 +1,15 @@
1
1
  # Changelog
2
2
 
3
- All notable changes to `@tenkicloud/mcp`. This project follows semantic versioning.
3
+ All notable changes to `@luxorai/mcp` (also published as `@tenkicloud/mcp`). This project follows semantic versioning.
4
+
5
+ ## [0.4.2] - 2026-11-16
6
+
7
+ - The Docker image builds and runs on Node 22.23.5, from the Node.js 2026-11-11 security release, pinned by digest.
8
+ - Dependency install scripts are blocked (`npm ci --ignore-scripts`, `strict-allow-scripts`).
9
+
10
+ ## [0.4.1] - 2026-11-12
11
+
12
+ - Package page now shows Luxor names, install commands and links.
4
13
 
5
14
  ## [0.4.0] - 2026-11-10
6
15
 
package/README.md CHANGED
@@ -1,8 +1,10 @@
1
- # tenki-mcp — `@tenkicloud/mcp`
1
+ # Luxor MCP: `@luxorai/mcp`
2
2
 
3
- **A [Model Context Protocol](https://modelcontextprotocol.io) server for [Tenki Cloud](https://tenki.cloud).** Give any agent — Claude, Codex, Cursor — a disposable microVM it can create, run code in, read and write files, run git, and expose to the web. Sandboxes boot in ~2 seconds and are billed per second.
3
+ **A [Model Context Protocol](https://modelcontextprotocol.io) server for [Luxor Sandbox](https://luxor.ai), part of Luxor Agent Cloud by Luxor AI.** Give any agent (Claude, Codex, Cursor) a disposable microVM it can create, run code in, read and write files, run git, and expose to the web. Sandboxes boot in ~2 seconds and are billed per second.
4
4
 
5
- Part of making Tenki the execution layer coding agents reach for: the agent writes code and Tenki runs it in isolation. (Tenki's **Code Reviewer** and **Runners** — AI PR review and managed CI — are separate products; this server currently exposes the Sandbox.)
5
+ The agent writes code and Luxor runs it in isolation. (**Luxor Code Review** and Luxor's managed CI runners are separate products; this server currently exposes the Sandbox.)
6
+
7
+ The old `@tenkicloud/mcp` name keeps working and publishes the same code.
6
8
 
7
9
  ```
8
10
  "Run this Python in a fresh sandbox and tell me what it prints."
@@ -14,19 +16,19 @@ Part of making Tenki the execution layer coding agents reach for: the agent writ
14
16
  ## Quickstart
15
17
 
16
18
  ```bash
17
- export TENKI_API_KEY=tk_your_key_here
18
- npx -y @tenkicloud/mcp # speaks MCP over stdio
19
+ export LUXORAI_API_KEY=lx_your_key_here
20
+ npx -y @luxorai/mcp # speaks MCP over stdio
19
21
  ```
20
22
 
21
- Nothing to clone or build. The package installs one command, `tenki-mcp`.
23
+ Nothing to clone or build. The package installs the command `luxor-mcp` (and `tenki-mcp`, the same program).
22
24
 
23
25
  ### Use it in Claude Code
24
26
 
25
- Connect to Tenki's hosted MCP service and sign in with your Tenki account:
27
+ Connect to Luxor's hosted MCP service and sign in with your Luxor account:
26
28
 
27
29
  ```bash
28
- claude mcp add --transport http tenki https://mcp.tenki.cloud/mcp
29
- claude mcp login tenki
30
+ claude mcp add --transport http luxor https://mcp.luxor.ai/mcp
31
+ claude mcp login luxor
30
32
  ```
31
33
 
32
34
  Claude Code's `mcp add` command stores the server configuration; `mcp login` performs the one-time browser authorization and workspace selection.
@@ -34,18 +36,20 @@ Claude Code's `mcp add` command stores the server configuration; `mcp login` per
34
36
  Alternatively, run the MCP server locally with an API key:
35
37
 
36
38
  ```bash
37
- claude mcp add tenki --env TENKI_API_KEY=tk_your_key_here -- npx -y @tenkicloud/mcp
39
+ claude mcp add luxor --env LUXORAI_API_KEY=lx_your_key_here -- npx -y @luxorai/mcp
38
40
  ```
39
41
 
40
42
  ### Or install it as a Claude Code plugin
41
43
 
42
- The repo doubles as a plugin marketplace. This prompts for your API key on install and stores it in your OS keychain — no env var to manage:
44
+ The repo doubles as a plugin marketplace. This prompts for your API key on install and stores it in your OS keychain, so there is no env var to manage:
43
45
 
44
46
  ```
45
47
  /plugin marketplace add LuxorLabs/tenki-mcp
46
- /plugin install tenki@tenki
48
+ /plugin install luxor@tenki
47
49
  ```
48
50
 
51
+ The `tenki@tenki` plugin is still available.
52
+
49
53
  ### Use it in Claude Desktop
50
54
 
51
55
  Add to `claude_desktop_config.json`:
@@ -53,10 +57,10 @@ Add to `claude_desktop_config.json`:
53
57
  ```json
54
58
  {
55
59
  "mcpServers": {
56
- "tenki": {
60
+ "luxor": {
57
61
  "command": "npx",
58
- "args": ["-y", "@tenkicloud/mcp"],
59
- "env": { "TENKI_API_KEY": "tk_your_key_here" }
62
+ "args": ["-y", "@luxorai/mcp"],
63
+ "env": { "LUXORAI_API_KEY": "lx_your_key_here" }
60
64
  }
61
65
  }
62
66
  }
@@ -69,10 +73,10 @@ Add the same block to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (glob
69
73
  ```json
70
74
  {
71
75
  "mcpServers": {
72
- "tenki": {
76
+ "luxor": {
73
77
  "command": "npx",
74
- "args": ["-y", "@tenkicloud/mcp"],
75
- "env": { "TENKI_API_KEY": "tk_your_key_here" }
78
+ "args": ["-y", "@luxorai/mcp"],
79
+ "env": { "LUXORAI_API_KEY": "lx_your_key_here" }
76
80
  }
77
81
  }
78
82
  }
@@ -83,22 +87,22 @@ Add the same block to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (glob
83
87
  The OpenAI Codex CLI reads MCP servers from `~/.codex/config.toml`. Add:
84
88
 
85
89
  ```toml
86
- [mcp_servers.tenki]
90
+ [mcp_servers.luxor]
87
91
  command = "npx"
88
- args = ["-y", "@tenkicloud/mcp"]
89
- env = { TENKI_API_KEY = "tk_your_key_here" }
92
+ args = ["-y", "@luxorai/mcp"]
93
+ env = { LUXORAI_API_KEY = "lx_your_key_here" }
90
94
  ```
91
95
 
92
96
  ### Confirm it's working
93
97
 
94
98
  After adding the server, **start a fresh session** so the client loads it, then ask your agent one of:
95
99
 
96
- - *"Check tenki auth status."* — confirms your credential was picked up.
97
- - *"Run `print(2+2)` in a fresh Tenki sandbox."* — a full boot → run → teardown round-trip.
100
+ - _"Check tenki auth status."_: confirms your credential was picked up.
101
+ - _"Run `print(2+2)` in a fresh Luxor sandbox."_: a full boot → run → teardown round-trip.
98
102
 
99
103
  If the `tenki_*` tools don't show up, restart the client so it re-reads its config.
100
104
 
101
- No key yet? Start the server without one and ask the agent to check `tenki_auth_status` — it reports what to set and where. See [Auth](#auth).
105
+ No key yet? Start the server without one and ask the agent to check `tenki_auth_status`; it reports what to set and where. See [Auth](#auth).
102
106
 
103
107
  ### Run it from a clone instead
104
108
 
@@ -107,56 +111,56 @@ For development, or to run an unreleased change:
107
111
  ```bash
108
112
  git clone https://github.com/LuxorLabs/tenki-mcp.git && cd tenki-mcp
109
113
  npm install && npm run build
110
- TENKI_API_KEY=tk_your_key_here node dist/index.js
114
+ LUXORAI_API_KEY=lx_your_key_here node dist/index.js
111
115
  ```
112
116
 
113
117
  Substitute `node /absolute/path/to/tenki-mcp/dist/index.js` for the `npx` command in any of the configs above. See [CONTRIBUTING.md](CONTRIBUTING.md) for the full development loop.
114
118
 
115
119
  ### Environment variables
116
120
 
117
- | Variable | Default | Purpose |
118
- |---|---|---|
119
- | `TENKI_API_KEY` | — | API key (`tk_…`). One of this or `TENKI_AUTH_TOKEN` is required. |
120
- | `TENKI_AUTH_TOKEN` | — | Session token (`ory_st_…` or cookie value). **Takes precedence over `TENKI_API_KEY`** when both are set. |
121
- | `TENKI_API_ENDPOINT` | `https://api.tenki.cloud` | Control-plane base URL (`TENKI_API_URL` is an alias). |
122
- | `TENKI_MCP_READONLY` | off | `1` registers only read tools (no create/run/delete/spend). |
123
- | `TENKI_MCP_DISABLED_TOOLS` | — | Comma-separated tool names to skip registering. |
124
- | `TENKI_MCP_AUDIT` | off | `1` logs each tool call name + arg keys to stderr. |
125
- | `TENKI_MCP_TRANSPORT` | `stdio` | `http` serves Streamable HTTP instead (see below). |
126
- | `PORT` | `3000` | HTTP transport port. |
127
- | `TENKI_MCP_HTTP_HOST` | `127.0.0.1` | HTTP bind host; non-loopback requires `TENKI_MCP_HTTP_TOKEN`. |
128
- | `TENKI_MCP_HTTP_TOKEN` | — | Bearer token for the HTTP endpoint; optional on loopback, required on a non-loopback host. |
129
- | `TENKI_MCP_PUBLIC_URL` | — | Public base URL for an OAuth-protected hosted server. |
130
- | `TENKI_MCP_OAUTH_ISSUER` | — | OAuth authorization-server issuer. Enables delegated OAuth HTTP mode. |
131
- | `TENKI_MCP_OAUTH_RESOURCE` | `<public URL>/mcp` | RFC 8707 resource identifier accepted in access-token audiences. A comma-separated list serves one resource per domain; metadata returns the one matching the request host, else the first. |
132
- | `TENKI_MCP_OAUTH_SCOPE` | `mcp` | Required delegated scope. |
133
- | `TENKI_MCP_IDENTITY_URL` | — | Internal Tenki Identity service endpoint used to exchange OAuth access tokens. |
134
- | `TENKI_MCP_IDENTITY_SERVICE_TOKEN` | — | Service credential for the private Identity token-exchange RPC. |
135
-
136
- Every `TENKI_*` variable above also has a `LUXORAI_*` equivalent (for example `LUXORAI_API_KEY`, `LUXORAI_MCP_TRANSPORT`). All `LUXORAI_*` credentials are read before any `TENKI_*` one, and `lx_…` API keys are accepted alongside `tk_…`.
121
+ | Variable | Default | Purpose |
122
+ | ------------------------------------ | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
123
+ | `LUXORAI_API_KEY` | - | API key (`lx_…`, or `tk_…`). One of this or `LUXORAI_AUTH_TOKEN` is required. |
124
+ | `LUXORAI_AUTH_TOKEN` | - | Session token (`ory_st_…` or cookie value). **Takes precedence over `LUXORAI_API_KEY`** when both are set. |
125
+ | `LUXORAI_API_ENDPOINT` | `https://api.tenki.cloud` (the same API as `https://api.luxor.ai`) | Control-plane base URL (`LUXORAI_API_URL` is an alias). |
126
+ | `LUXORAI_MCP_READONLY` | off | `1` registers only read tools (no create/run/delete/spend). |
127
+ | `LUXORAI_MCP_DISABLED_TOOLS` | - | Comma-separated tool names to skip registering. |
128
+ | `LUXORAI_MCP_AUDIT` | off | `1` logs each tool call name + arg keys to stderr. |
129
+ | `LUXORAI_MCP_TRANSPORT` | `stdio` | `http` serves Streamable HTTP instead (see below). |
130
+ | `PORT` | `3000` | HTTP transport port. |
131
+ | `LUXORAI_MCP_HTTP_HOST` | `127.0.0.1` | HTTP bind host; non-loopback requires `LUXORAI_MCP_HTTP_TOKEN`. |
132
+ | `LUXORAI_MCP_HTTP_TOKEN` | - | Bearer token for the HTTP endpoint; optional on loopback, required on a non-loopback host. |
133
+ | `LUXORAI_MCP_PUBLIC_URL` | - | Public base URL for an OAuth-protected hosted server. |
134
+ | `LUXORAI_MCP_OAUTH_ISSUER` | - | OAuth authorization-server issuer. Enables delegated OAuth HTTP mode. |
135
+ | `LUXORAI_MCP_OAUTH_RESOURCE` | `<public URL>/mcp` | RFC 8707 resource identifier accepted in access-token audiences. A comma-separated list serves one resource per domain; metadata returns the one matching the request host, else the first. |
136
+ | `LUXORAI_MCP_OAUTH_SCOPE` | `mcp` | Required delegated scope. |
137
+ | `LUXORAI_MCP_IDENTITY_URL` | - | Internal Luxor Identity service endpoint used to exchange OAuth access tokens. |
138
+ | `LUXORAI_MCP_IDENTITY_SERVICE_TOKEN` | - | Service credential for the private Identity token-exchange RPC. |
139
+
140
+ Every `LUXORAI_*` variable above is still accepted under its `TENKI_*` name (for example `TENKI_API_KEY`, `TENKI_MCP_TRANSPORT`). All `LUXORAI_*` credentials are read before any `TENKI_*` one. Keys start with `lx_`; `tk_…` keys are still accepted.
137
141
 
138
142
  ## Tools
139
143
 
140
- **82 tools** — all 76 tool-worthy public unary API methods (enforced by a CI [parity audit](scripts/parity-audit.mjs), which also fails if a tool calls a method the API no longer has; `GitOperation` is exposed as one tool per operation), two workflow helpers, and `tenki_auth_status`. A few admin surfaces (published images, saved Tailscale connections) and implementation-only control-plane methods are intentionally excluded. Grouped by domain:
141
-
142
- | Domain | Tools |
143
- |---|---|
144
- | **Auth** | `tenki_auth_status` (which credential is configured, and does it work — the only tool available when none is) |
145
- | **Identity** | `tenki_whoami` |
146
- | **Run** | `tenki_run_code` (one-shot: boot → run shell/python/js → tear down) |
147
- | **Sandboxes** | `tenki_create_sandbox` · `tenki_get_sandbox` · `tenki_get_sandbox_metrics` · `tenki_list_sandboxes` · `tenki_terminate_sandbox` · `tenki_pause_sandbox` · `tenki_resume_sandbox` · `tenki_fork_sandbox` (copies of a running sandbox) |
148
- | **Session admin** | `tenki_extend_sandbox` · `tenki_update_sandbox` · `tenki_terminate_sandboxes` (bulk) · `tenki_report_sandbox_activity` · `tenki_list_workspace_sandboxes` |
149
- | **Exec** | `tenki_exec` (stdout/stderr/exit inline) |
150
- | **Files** | `tenki_read_file` · `tenki_write_file` · `tenki_list_files` · `tenki_stat_path` · `tenki_make_dir` · `tenki_remove_path` · `tenki_move_path` |
151
- | **Git** | `tenki_git_clone` · `tenki_git_checkout` · `tenki_git_diff` · `tenki_git_log` (the four operations the API supports; pass `directory` to target a cloned repo; run other git commands via `tenki_exec`) |
152
- | **Ports & previews** | expose · list-exposed · unexpose · create-preview-url · open-preview (viewer-token-gated, not public; port 7681 is the web terminal) · list/get/delete-preview-url · touch-preview · bind/unbind-preview-url · resolve-preview-token |
153
- | **Artifacts** (binary transfer) | `tenki_get_upload_url` · `tenki_get_download_url` (signed URLs for binary PUT/GET) |
154
- | **SSH** | `tenki_update_ssh_keys` · `tenki_issue_ssh_cert` · `tenki_list_ssh_gateways` |
155
- | **Snapshots** | create · get · list · list-session · list-workspace · list-dangling · update · delete · get-download-url |
156
- | **Volumes** | create · get · list · update · delete · resize · attach · detach |
157
- | **Egress policies** | create · get · list · update · delete (named workspace allowlists that `tenki_create_sandbox` pins via `egress_policies`) |
158
- | **Templates** | create · get · list · update · delete · build · cancel-build · get-build · list-active-builds · list-builds · delete-build |
159
- | **Workspace** | `tenki_get_workspace_usage` · `tenki_list_ci_runner_sizes` · `tenki_get_workspace_preview_domains` · `tenki_update_workspace_preview_domains` |
144
+ **82 tools**: all 76 tool-worthy public unary API methods (enforced by a CI [parity audit](scripts/parity-audit.mjs), which also fails if a tool calls a method the API no longer has; `GitOperation` is exposed as one tool per operation), two workflow helpers, and `tenki_auth_status`. Tool names keep the `tenki_` prefix. A few admin surfaces (published images, saved Tailscale connections) and implementation-only control-plane methods are intentionally excluded. Grouped by domain:
145
+
146
+ | Domain | Tools |
147
+ | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
148
+ | **Auth** | `tenki_auth_status` (which credential is configured, and does it work; the only tool available when none is) |
149
+ | **Identity** | `tenki_whoami` |
150
+ | **Run** | `tenki_run_code` (one-shot: boot → run shell/python/js → tear down) |
151
+ | **Sandboxes** | `tenki_create_sandbox` · `tenki_get_sandbox` · `tenki_get_sandbox_metrics` · `tenki_list_sandboxes` · `tenki_terminate_sandbox` · `tenki_pause_sandbox` · `tenki_resume_sandbox` · `tenki_fork_sandbox` (copies of a running sandbox) |
152
+ | **Session admin** | `tenki_extend_sandbox` · `tenki_update_sandbox` · `tenki_terminate_sandboxes` (bulk) · `tenki_report_sandbox_activity` · `tenki_list_workspace_sandboxes` |
153
+ | **Exec** | `tenki_exec` (stdout/stderr/exit inline) |
154
+ | **Files** | `tenki_read_file` · `tenki_write_file` · `tenki_list_files` · `tenki_stat_path` · `tenki_make_dir` · `tenki_remove_path` · `tenki_move_path` |
155
+ | **Git** | `tenki_git_clone` · `tenki_git_checkout` · `tenki_git_diff` · `tenki_git_log` (the four operations the API supports; pass `directory` to target a cloned repo; run other git commands via `tenki_exec`) |
156
+ | **Ports & previews** | expose · list-exposed · unexpose · create-preview-url · open-preview (viewer-token-gated, not public; port 7681 is the web terminal) · list/get/delete-preview-url · touch-preview · bind/unbind-preview-url · resolve-preview-token |
157
+ | **Artifacts** (binary transfer) | `tenki_get_upload_url` · `tenki_get_download_url` (signed URLs for binary PUT/GET) |
158
+ | **SSH** | `tenki_update_ssh_keys` · `tenki_issue_ssh_cert` · `tenki_list_ssh_gateways` |
159
+ | **Snapshots** | create · get · list · list-session · list-workspace · list-dangling · update · delete · get-download-url |
160
+ | **Volumes** | create · get · list · update · delete · resize · attach · detach |
161
+ | **Egress policies** | create · get · list · update · delete (named workspace allowlists that `tenki_create_sandbox` pins via `egress_policies`) |
162
+ | **Templates** | create · get · list · update · delete · build · cancel-build · get-build · list-active-builds · list-builds · delete-build |
163
+ | **Workspace** | `tenki_get_workspace_usage` · `tenki_list_ci_runner_sizes` · `tenki_get_workspace_preview_domains` · `tenki_update_workspace_preview_domains` |
160
164
 
161
165
  Full per-release breakdown in [CHANGELOG.md](CHANGELOG.md).
162
166
 
@@ -164,38 +168,38 @@ Full per-release breakdown in [CHANGELOG.md](CHANGELOG.md).
164
168
 
165
169
  ## Auth
166
170
 
167
- Set one of `TENKI_API_KEY` or `TENKI_AUTH_TOKEN` — when both are set, `TENKI_AUTH_TOKEN` wins. The header is chosen by token prefix: `tk_…` → `Authorization: Bearer`, `ory_st_…` → `X-Session-Token`, otherwise a session cookie. Override the endpoint with `TENKI_API_ENDPOINT` (default `https://api.tenki.cloud`).
171
+ Set one of `LUXORAI_API_KEY` or `LUXORAI_AUTH_TOKEN` (`TENKI_API_KEY` / `TENKI_AUTH_TOKEN` are still accepted). When both are set, the auth token wins. The header is chosen by token prefix: `lx_…` or `tk_…` → `Authorization: Bearer`, `ory_st_…` → `X-Session-Token`, otherwise a session cookie. Override the endpoint with `LUXORAI_API_ENDPOINT` (default `https://api.tenki.cloud`, the same API as `https://api.luxor.ai`).
168
172
 
169
- **Without a credential the server still starts**, registering only `tenki_auth_status` — so instead of an MCP client reporting an opaque "server failed to start", the agent can call that tool and get told what to set. Ask it "check tenki auth status" any time other tools return auth errors: it reports the credential kind (API key vs session token), the endpoint, and whether a live identity probe succeeded — never the token itself. It reports status only; get a credential with `tenki login` or from the dashboard.
173
+ **Without a credential the server still starts**, registering only `tenki_auth_status`, so instead of an MCP client reporting an opaque "server failed to start", the agent can call that tool and get told what to set. Ask it "check tenki auth status" any time other tools return auth errors: it reports the credential kind (API key vs session token), the endpoint, and whether a live identity probe succeeded, never the token itself. It reports status only; get a credential from the Luxor dashboard.
170
174
 
171
175
  ## Host it over HTTP (v2.0-beta)
172
176
 
173
177
  Besides stdio, the server speaks **Streamable HTTP** so it can be hosted for remote MCP clients:
174
178
 
175
179
  ```bash
176
- TENKI_MCP_TRANSPORT=http PORT=3000 TENKI_API_KEY=… npx -y @tenkicloud/mcp
180
+ LUXORAI_MCP_TRANSPORT=http PORT=3000 LUXORAI_API_KEY=… npx -y @luxorai/mcp
177
181
  # → tenki-mcp running on http://127.0.0.1:3000/mcp (Streamable HTTP) [loopback only, no auth]
178
182
  ```
179
183
 
180
- For a single-user deployment, HTTP mode can hold one shared `TENKI_API_KEY` and therefore exposes a powerful capability. By default it:
184
+ For a single-user deployment, HTTP mode can hold one shared `LUXORAI_API_KEY` and therefore exposes a powerful capability. By default it:
181
185
 
182
- - **binds to loopback (`127.0.0.1`) only** — set `TENKI_MCP_HTTP_HOST=0.0.0.0` to expose it, but then
183
- - it **requires a bearer token**: set `TENKI_MCP_HTTP_TOKEN` and send `Authorization: Bearer <token>`. It **refuses to start** on a non-loopback host without one.
186
+ - **binds to loopback (`127.0.0.1`) only**: set `LUXORAI_MCP_HTTP_HOST=0.0.0.0` to expose it, but then
187
+ - it **requires a bearer token**: set `LUXORAI_MCP_HTTP_TOKEN` and send `Authorization: Bearer <token>`. It **refuses to start** on a non-loopback host without one.
184
188
  - **DNS-rebinding protection** is on (Host-header allowlist), so a malicious web page can't drive your local server.
185
189
 
186
190
  ```bash
187
191
  # expose to a network safely:
188
- TENKI_MCP_TRANSPORT=http TENKI_MCP_HTTP_HOST=0.0.0.0 PORT=3000 \
189
- TENKI_MCP_HTTP_TOKEN=$(openssl rand -hex 32) TENKI_API_KEY=… npx -y @tenkicloud/mcp
192
+ LUXORAI_MCP_TRANSPORT=http LUXORAI_MCP_HTTP_HOST=0.0.0.0 PORT=3000 \
193
+ LUXORAI_MCP_HTTP_TOKEN=$(openssl rand -hex 32) LUXORAI_API_KEY=… npx -y @luxorai/mcp
190
194
  ```
191
195
 
192
- Point an HTTP-capable MCP client at `/mcp`. Static-key mode uses one shared `TENKI_API_KEY` for all sessions. Verified end-to-end (`test/http-transport.test.mjs`: auth gate, DNS-rebinding rejection, connect → tools/list → tool call over HTTP).
196
+ Point an HTTP-capable MCP client at `/mcp`. Static-key mode uses one shared `LUXORAI_API_KEY` for all sessions. Verified end-to-end (`test/http-transport.test.mjs`: auth gate, DNS-rebinding rejection, connect → tools/list → tool call over HTTP).
193
197
 
194
- Hosted multi-tenant deployments instead use Tenki Identity's OAuth facade. The MCP server publishes RFC 9728 protected-resource metadata and exchanges each caller's access token through the private Identity service. Identity owns Hydra, validates the requested audience and scope, and issues a short-lived API delegation bound to the user, client, and workspace selected on the Tenki consent page. `tenki-mcp` has no Hydra Admin access and does not hold the delegation-signing secret.
198
+ Hosted multi-tenant deployments instead use Luxor Identity's OAuth facade. The MCP server publishes RFC 9728 protected-resource metadata and exchanges each caller's access token through the private Identity service. Identity owns Hydra, validates the requested audience and scope, and issues a short-lived API delegation bound to the user, client, and workspace selected on the Luxor consent page. `tenki-mcp` has no Hydra Admin access and does not hold the delegation-signing secret.
195
199
 
196
200
  ## How it works
197
201
 
198
- Tenki's API is **ConnectRPC** — JSON over HTTP/1.1, not REST. Every control-plane call is `POST https://api.tenki.cloud/tenki.sandbox.v1.SandboxService/{Method}` with a lowerCamelCase JSON body. Per-session file I/O runs on a **separate data-plane endpoint** returned at create time, authenticated with a short-lived session certificate. This server owns both transports so the tools stay one-liners.
202
+ Luxor's API is **ConnectRPC**: JSON over HTTP/1.1, not REST. Every control-plane call is `POST https://api.luxor.ai/tenki.sandbox.v1.SandboxService/{Method}` with a lowerCamelCase JSON body. Per-session file I/O runs on a **separate data-plane endpoint** returned at create time, authenticated with a short-lived session certificate. This server owns both transports so the tools stay one-liners.
199
203
 
200
204
  Command output: `tenki_exec` and `tenki_run_code` capture `stdout`/`stderr` by redirecting to files (`sh -c '… > out 2> err'`) and reading them back over the data plane, so you get the output inline through a plain HTTP client.
201
205
 
@@ -203,19 +207,19 @@ The wire details are ported from the live-verified [n8n community node](https://
203
207
 
204
208
  ## Security
205
209
 
206
- This server holds a Tenki API key and can run code + spend credits, so treat it as a capability. Full model + [CSA MCP Server Top-10](https://modelcontextprotocol-security.io/top10/server/) mapping in **[SECURITY.md](SECURITY.md)**. Quick controls:
210
+ This server holds a Luxor API key and can run code + spend credits, so treat it as a capability. Full model + [CSA MCP Server Top-10](https://modelcontextprotocol-security.io/top10/server/) mapping in **[SECURITY.md](SECURITY.md)**. Quick controls:
207
211
 
208
- - **Least privilege:** every tool carries a title and MCP annotations: `readOnlyHint` on reads, and `destructiveHint` on every tool that can overwrite, modify, interrupt or delete existing state (only tools that create, resume, extend, attach or keep alive without changing existing state are non-destructive). Run `TENKI_MCP_READONLY=1` for an inspection-only server (read tools only), or `TENKI_MCP_DISABLED_TOOLS=tenki_run_code,…` to drop specific tools.
212
+ - **Least privilege:** every tool carries a title and MCP annotations: `readOnlyHint` on reads, and `destructiveHint` on every tool that can overwrite, modify, interrupt or delete existing state (only tools that create, resume, extend, attach or keep alive without changing existing state are non-destructive). Run `LUXORAI_MCP_READONLY=1` for an inspection-only server (read tools only), or `LUXORAI_MCP_DISABLED_TOOLS=tenki_run_code,…` to drop specific tools.
209
213
  - **HTTP transport** is loopback-only by default and requires a bearer token to expose to a network (see [Host it over HTTP](#host-it-over-http-v20-beta)).
210
- - **Audit:** `TENKI_MCP_AUDIT=1` logs each tool call's name to stderr.
211
- - **Untrusted output:** `tenki_run_code`/`tenki_exec`/`tenki_read_file` return output from untrusted code — clients should treat tool results as data, not instructions.
214
+ - **Audit:** `LUXORAI_MCP_AUDIT=1` logs each tool call's name to stderr.
215
+ - **Untrusted output:** `tenki_run_code`/`tenki_exec`/`tenki_read_file` return output from untrusted code; clients should treat tool results as data, not instructions.
212
216
 
213
217
  Report vulnerabilities via a private [security advisory](https://github.com/LuxorLabs/tenki-mcp/security/advisories/new), not a public issue.
214
218
 
215
219
  ## Related
216
220
 
217
- - **Tenki Sandbox** — the platform: https://tenki.cloud
218
- - **n8n-nodes-tenki** — Tenki as an n8n node: https://github.com/opencolin/n8n-nodes-tenki
221
+ - **Luxor Sandbox**, the platform: https://luxor.ai
222
+ - **n8n-nodes-tenki**, Luxor Sandbox as an n8n node: https://github.com/opencolin/n8n-nodes-tenki
219
223
 
220
224
  ## License
221
225
 
package/dist/server.d.ts CHANGED
@@ -15,7 +15,7 @@
15
15
  */
16
16
  import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
17
17
  import type { TenkiClient } from "./client.js";
18
- export declare const VERSION = "0.4.0";
18
+ export declare const VERSION = "0.4.2";
19
19
  /**
20
20
  * Tool classes, mapped to MCP annotations by annotationsFor():
21
21
  * read → readOnlyHint: true. Pure inspection: no state change, no spend.
package/dist/server.js CHANGED
@@ -34,7 +34,7 @@ import { registerEgress } from "./tools/egress.js";
34
34
  import { registerAuthStatus } from "./tools/auth_status.js";
35
35
  import { readEnv } from "./env.js";
36
36
  import { TOOL_TITLES } from "./tools/titles.js";
37
- export const VERSION = "0.4.0";
37
+ export const VERSION = "0.4.2";
38
38
  const modules = [
39
39
  registerIdentity,
40
40
  registerRun,
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@tenkicloud/mcp",
3
- "version": "0.4.0",
3
+ "version": "0.4.2",
4
4
  "mcpName": "io.github.LuxorLabs/tenki-mcp",
5
- "description": "Model Context Protocol server for Tenki Cloud — disposable microVM sandboxes for AI agents. Create sandboxes, run code, read/write files, run git, expose preview URLs — from any MCP client.",
5
+ "description": "Model Context Protocol server for Luxor Sandbox (Luxor Agent Cloud): disposable microVM sandboxes for AI agents. Create sandboxes, run code, read/write files, run git, expose preview URLs, from any MCP client.",
6
6
  "type": "module",
7
7
  "bin": {
8
8
  "tenki-mcp": "dist/index.js",
@@ -27,16 +27,19 @@
27
27
  "test:offline": "npm run build && node test/offline.test.mjs"
28
28
  },
29
29
  "keywords": [
30
- "tenki",
30
+ "luxor",
31
+ "luxor-ai",
32
+ "luxor-agent-cloud",
31
33
  "mcp",
32
34
  "model-context-protocol",
33
35
  "sandbox",
34
36
  "microvm",
35
37
  "ai-agents",
36
- "code-execution"
38
+ "code-execution",
39
+ "tenki"
37
40
  ],
38
41
  "license": "MIT",
39
- "author": "Tenki Cloud (https://tenki.cloud)",
42
+ "author": "Luxor AI (https://luxor.ai)",
40
43
  "publishConfig": {
41
44
  "access": "public"
42
45
  },
@@ -55,7 +58,7 @@
55
58
  "type": "git",
56
59
  "url": "git+https://github.com/LuxorLabs/tenki-mcp.git"
57
60
  },
58
- "homepage": "https://github.com/LuxorLabs/tenki-mcp#readme",
61
+ "homepage": "https://luxor.ai",
59
62
  "bugs": {
60
63
  "url": "https://github.com/LuxorLabs/tenki-mcp/issues"
61
64
  }