naro-mcp 0.11.0 → 0.12.0
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/README.md +42 -29
- package/dist/index.js +1019 -24
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -2,9 +2,11 @@
|
|
|
2
2
|
|
|
3
3
|
MCP server that lets AI agents (Claude Code, Cursor, Codex, ChatGPT, …)
|
|
4
4
|
operate [Naro](https://naro.sh): deploy projects, read build/runtime logs,
|
|
5
|
-
manage environment variables and domains, promote and roll back,
|
|
6
|
-
|
|
7
|
-
|
|
5
|
+
manage environment variables and domains, promote and roll back, work with
|
|
6
|
+
the project's database (SQL, migrations, types, export and restore), and
|
|
7
|
+
read Speed Insights and turn it on or off, read or switch preview protection,
|
|
8
|
+
and manage Storage buckets — the same control plane API the `naro` CLI uses,
|
|
9
|
+
via the shared SDK.
|
|
8
10
|
|
|
9
11
|
Deployable projects: Next.js **15 or newer** (Next 14 and below are not
|
|
10
12
|
supported), Vite, Create React App and plain static sites.
|
|
@@ -52,26 +54,32 @@ Headless/CI agents can skip `naro login` and set a token instead:
|
|
|
52
54
|
|
|
53
55
|
## Tools
|
|
54
56
|
|
|
55
|
-
| Tool
|
|
56
|
-
|
|
|
57
|
-
| `whoami`, `list_teams`
|
|
58
|
-
| `list_projects`, `get_project`, `link_project`
|
|
59
|
-
| `deploy`
|
|
60
|
-
| `list_deployments`, `get_deployment`
|
|
61
|
-
| `get_build_logs`, `get_runtime_logs`
|
|
62
|
-
| `list_environment_variables`, `set_environment_variable`, `remove_environment_variable`
|
|
63
|
-
| `list_domains`, `add_domain`, `verify_domain`, `remove_domain`
|
|
64
|
-
| `promote_deployment`, `rollback_deployment`
|
|
65
|
-
| `cancel_deployment`
|
|
66
|
-
| `enable_database`, `get_database`, `list_tables`
|
|
67
|
-
| `execute_sql`
|
|
68
|
-
| `apply_migration`, `list_migrations`, `generate_typescript_types`
|
|
69
|
-
| `create_table`, `alter_table`, `drop_table`, `create_index`, `drop_index`
|
|
70
|
-
| `export_database`
|
|
71
|
-
| `restore_database`
|
|
57
|
+
| Tool | Purpose |
|
|
58
|
+
| ---------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
59
|
+
| `whoami`, `list_teams` | Account / team context |
|
|
60
|
+
| `list_projects`, `get_project`, `link_project` | Project discovery + `.naro/project.json` linking |
|
|
61
|
+
| `deploy` | Local Next.js build → upload → live URL (preview or `production: true`). Local .env files are never uploaded; unset keys come back as `missingEnvKeys` |
|
|
62
|
+
| `list_deployments`, `get_deployment` | Deployment status / history |
|
|
63
|
+
| `get_build_logs`, `get_runtime_logs` | Debugging failed builds and live workers |
|
|
64
|
+
| `list_environment_variables`, `set_environment_variable`, `remove_environment_variable` | Env management (secret values never returned) |
|
|
65
|
+
| `list_domains`, `add_domain`, `verify_domain`, `remove_domain` | Custom domains: every DNS record to create, plus a re-check that says which of ownership / certificate / routing is still missing. An apex is attached as an apex+www pair by default (`withWww: false` to opt out) |
|
|
66
|
+
| `promote_deployment`, `rollback_deployment` | Production traffic control |
|
|
67
|
+
| `cancel_deployment` | Stops a build that is still running (QUEUED–BUILDING). Does not undo a deployment that already went live — use `rollback_deployment` for that |
|
|
68
|
+
| `enable_database`, `get_database`, `list_tables` | The project's D1 database: turn it on, status/size/limits, schema (verbose: true for columns, indexes and foreign keys) |
|
|
69
|
+
| `execute_sql` | Run SQL (argument `query`, optional `params` for a single statement; several statements run as one transaction). Destructive; under `--read-only` it stays but accepts a single read statement only |
|
|
70
|
+
| `apply_migration`, `list_migrations`, `generate_typescript_types` | Numbered migrations in the `d1_migrations` ledger wrangler also uses (each file all-or-nothing), and TypeScript types for the schema (text only; its `Database` is what `createClient<Database>()` from `naro-js` takes) |
|
|
71
|
+
| `create_table`, `alter_table`, `drop_table`, `create_index`, `drop_index` | Schema changes without SQL: naro renders checked DDL, applies it as one numbered migration (`NNNN_schema_<op>_<table>.sql`) and writes the file like `apply_migration`. `alter_table` adds, renames or drops a column or renames the table. Dropping a table or column needs `confirm`; `alter_table`, `drop_table` and `drop_index` are destructive and hidden under `--read-only`. `dryRun: true` returns the SQL only |
|
|
72
|
+
| `export_database` | SQL dump of the database (`schemaOnly`, `dataOnly`, `tables`): waits up to 5 minutes and returns a signed download link plus `atBookmark`, the point the dump reflects |
|
|
73
|
+
| `restore_database` | Time Travel restore to a `bookmark` or a `timestamp` (last 30 days). Destructive; hidden under `--read-only`. Returns `previousBookmark`, which undoes it |
|
|
74
|
+
| `get_speed_insights`, `set_speed_insights` | Speed Insights: each Web Vital's p75, the selected metric by page, device, element and deployment, or one route's paths; production or preview (`environment`); turn measuring on or off (not destructive: nothing is deleted) |
|
|
75
|
+
| `get_preview_protection`, `set_preview_protection` | Preview protection: whether the preview URL (`{subdomain}-preview`) is open to project members only, and whether a bypass secret is set; turn it on or off. **`set_preview_protection` is destructive** (turning protection off publishes unreleased work). Bypass secrets are made in the dashboard or with `naro protection bypass`, never by a tool, so they stay out of the conversation |
|
|
76
|
+
| `get_storage`, `enable_storage`, `list_storage_buckets`, `create_storage_bucket`, `update_storage_bucket`, `delete_storage_bucket` | Naro Storage: on or off, limits, usage and buckets; turn it on; make, change and remove buckets (`delete_storage_bucket` is destructive: `confirm` is the bucket's name, `empty: true` deletes its objects first; `update_storage_bucket` is destructive on its `public` argument, like `deploy` on `production`: `public: true` needs the same `confirm`). Files go in through naro-js or `naro storage cp`, not through MCP |
|
|
72
77
|
|
|
73
78
|
Destructive tools say so in their descriptions; agents should confirm with
|
|
74
|
-
the user before calling them.
|
|
79
|
+
the user before calling them. `set_preview_protection` is one of them: turning
|
|
80
|
+
protection off publishes the preview to anyone with the link, so the marker
|
|
81
|
+
sits on its `enabled` argument and clients that confirm on `destructiveHint`
|
|
82
|
+
ask before either value. Domain tools return server-computed
|
|
75
83
|
`instructions`, `guidance` and `cause` — relay those to the user verbatim
|
|
76
84
|
rather than dictating DNS records from memory, because an apex domain
|
|
77
85
|
(`example.com`) cannot take the CNAME a subdomain does. That is also why
|
|
@@ -86,14 +94,19 @@ deploy again.
|
|
|
86
94
|
|
|
87
95
|
## Flags
|
|
88
96
|
|
|
89
|
-
| Flag | Env | Effect
|
|
90
|
-
| -------------------- | ---------------------- |
|
|
91
|
-
| `--read-only` | `NARO_MCP_READ_ONLY=1` | Hides every tool that changes something. `execute_sql` stays and the control plane refuses anything but a single read statement
|
|
92
|
-
| `--features <a,b,…>` | `NARO_MCP_FEATURES` | Only these groups: `account`, `deployments`, `logs`, `env`, `domains`, `git`, `database`. An unknown group is a startup error, not an empty server |
|
|
93
|
-
|
|
94
|
-
Results of the `database` tools
|
|
95
|
-
|
|
96
|
-
|
|
97
|
+
| Flag | Env | Effect |
|
|
98
|
+
| -------------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
99
|
+
| `--read-only` | `NARO_MCP_READ_ONLY=1` | Hides every tool that changes something. `execute_sql` stays and the control plane refuses anything but a single read statement |
|
|
100
|
+
| `--features <a,b,…>` | `NARO_MCP_FEATURES` | Only these groups: `account`, `deployments`, `logs`, `env`, `domains`, `git`, `database`, `insights`, `protection`, `storage`. An unknown group is a startup error, not an empty server |
|
|
101
|
+
|
|
102
|
+
Results of the `database` tools, of `get_speed_insights` and of every Storage
|
|
103
|
+
tool that answers bucket rows (`get_storage`, `enable_storage`,
|
|
104
|
+
`list_storage_buckets`, `create_storage_bucket`, `update_storage_bucket`) are
|
|
105
|
+
wrapped in `<untrusted-data-…>` boundaries with
|
|
106
|
+
a random id per call — rows, identifiers and SQLite error messages are bytes
|
|
107
|
+
your app's users may have written, Speed Insights' paths and element names
|
|
108
|
+
come from any visitor's browser, bucket rows live in the project's database
|
|
109
|
+
(which the app and `naro db query` can write), and an agent must not follow
|
|
97
110
|
instructions found in them.
|
|
98
111
|
|
|
99
112
|
Pass `--features` once, as one comma-separated list — a second `--features` is
|