nana800-mcp-server 1.2.0 → 1.3.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 +235 -122
- package/dist/index.js +990 -28
- package/package.json +10 -1
package/README.md
CHANGED
|
@@ -1,187 +1,280 @@
|
|
|
1
1
|
# nana800 MCP Server
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[](https://www.npmjs.com/package/nana800-mcp-server)
|
|
4
|
+
[](LICENSE)
|
|
4
5
|
|
|
5
|
-
|
|
6
|
+
Model Context Protocol (MCP) server for [nana800.io](https://nana800.io/en/), a no-code platform for backend logic and workflow automation. Workflows (called schemes) are built from trigger and action blocks (called nodes) in a visual editor: webhooks, timers, HTTP requests, Telegram, Google Sheets, GPT and other integrations.
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
8
|
+
With this server an AI assistant (Claude, Cursor, VS Code and any other MCP client) works with your nana800 account through the Public API:
|
|
9
|
+
|
|
10
|
+
- 🧱 creates projects and schemes, adds trigger and action blocks, configures and connects them
|
|
11
|
+
- 📤 exports and imports schemes as JSON, reads the OpenAPI document of scheme webhooks
|
|
12
|
+
- 🔍 reads the run history of schemes and of single blocks
|
|
13
|
+
- 💳 reads the payment account and its transactions
|
|
14
|
+
- 📈 builds analytics charts and dashboards from a request in words: lines, bars, funnels, retention, splits by a property, filters, public dashboard links
|
|
15
|
+
- 📊 exports analytics events and users to CSV or JSON Lines files
|
|
16
|
+
|
|
17
|
+
The server runs on your machine over stdio and calls `https://api.nana800.io` and `https://api.analytics.nana800.io` with your API key. 59 tools, Node.js 18 or newer.
|
|
18
|
+
|
|
19
|
+
## 🔑 Get an API key
|
|
12
20
|
|
|
13
|
-
|
|
21
|
+
1. Sign in at [cloud.nana800.io](https://cloud.nana800.io)
|
|
22
|
+
2. Open [cloud.nana800.io/settings](https://cloud.nana800.io/settings) and create or copy an API key
|
|
23
|
+
3. Put it into `MCP_API_KEY` in the client config below
|
|
14
24
|
|
|
15
|
-
|
|
16
|
-
2. Create or copy your API key
|
|
17
|
-
3. Use it in the configuration below
|
|
25
|
+
The key acts as your user: the tools see and change only the projects your account has access to.
|
|
18
26
|
|
|
19
|
-
##
|
|
27
|
+
## 🚀 Quick start
|
|
20
28
|
|
|
21
|
-
###
|
|
29
|
+
### Claude Desktop
|
|
30
|
+
|
|
31
|
+
Open Settings -> Developer -> Edit Config, or the file directly:
|
|
22
32
|
|
|
23
|
-
|
|
33
|
+
- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
|
|
34
|
+
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`
|
|
24
35
|
|
|
25
36
|
```json
|
|
26
37
|
{
|
|
27
38
|
"mcpServers": {
|
|
28
39
|
"nana800": {
|
|
29
40
|
"command": "npx",
|
|
30
|
-
"args": ["nana800-mcp-server"],
|
|
41
|
+
"args": ["-y", "nana800-mcp-server"],
|
|
31
42
|
"env": {
|
|
32
|
-
"MCP_API_KEY": "
|
|
33
|
-
"MCP_PROJECT_ID": "your_default_project_id",
|
|
34
|
-
"MCP_SCHEME_ID": "your_default_scheme_id",
|
|
35
|
-
"MCP_ANALYTICS_ORG_ID": "your_default_analytics_org_id"
|
|
43
|
+
"MCP_API_KEY": "your_api_key"
|
|
36
44
|
}
|
|
37
45
|
}
|
|
38
46
|
}
|
|
39
47
|
}
|
|
40
48
|
```
|
|
41
49
|
|
|
42
|
-
|
|
50
|
+
Restart Claude Desktop after saving.
|
|
43
51
|
|
|
44
|
-
|
|
52
|
+
### Claude Code
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
claude mcp add nana800 -e MCP_API_KEY=your_api_key -- npx -y nana800-mcp-server
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Add `--scope user` to use it in all your projects.
|
|
59
|
+
|
|
60
|
+
### Cursor
|
|
61
|
+
|
|
62
|
+
Add to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (one project):
|
|
45
63
|
|
|
46
64
|
```json
|
|
47
65
|
{
|
|
48
66
|
"mcpServers": {
|
|
49
67
|
"nana800": {
|
|
50
68
|
"command": "npx",
|
|
51
|
-
"args": ["nana800-mcp-server"],
|
|
69
|
+
"args": ["-y", "nana800-mcp-server"],
|
|
52
70
|
"env": {
|
|
53
|
-
"MCP_API_KEY": "
|
|
54
|
-
"MCP_PROJECT_ID": "your_default_project_id",
|
|
55
|
-
"MCP_SCHEME_ID": "your_default_scheme_id",
|
|
56
|
-
"MCP_ANALYTICS_ORG_ID": "your_default_analytics_org_id"
|
|
71
|
+
"MCP_API_KEY": "your_api_key"
|
|
57
72
|
}
|
|
58
73
|
}
|
|
59
74
|
}
|
|
60
75
|
}
|
|
61
76
|
```
|
|
62
77
|
|
|
63
|
-
### VS Code
|
|
78
|
+
### VS Code
|
|
64
79
|
|
|
65
|
-
Add to
|
|
80
|
+
Add to `.vscode/mcp.json`. VS Code asks for the key on the first start and keeps it in its secret storage:
|
|
66
81
|
|
|
67
82
|
```json
|
|
68
83
|
{
|
|
69
|
-
"
|
|
84
|
+
"inputs": [
|
|
85
|
+
{
|
|
86
|
+
"type": "promptString",
|
|
87
|
+
"id": "nana800-api-key",
|
|
88
|
+
"description": "nana800.io API key",
|
|
89
|
+
"password": true
|
|
90
|
+
}
|
|
91
|
+
],
|
|
92
|
+
"servers": {
|
|
70
93
|
"nana800": {
|
|
94
|
+
"type": "stdio",
|
|
71
95
|
"command": "npx",
|
|
72
|
-
"args": ["nana800-mcp-server"],
|
|
96
|
+
"args": ["-y", "nana800-mcp-server"],
|
|
73
97
|
"env": {
|
|
74
|
-
"MCP_API_KEY": "
|
|
75
|
-
"MCP_PROJECT_ID": "your_default_project_id",
|
|
76
|
-
"MCP_SCHEME_ID": "your_default_scheme_id",
|
|
77
|
-
"MCP_ANALYTICS_ORG_ID": "your_default_analytics_org_id"
|
|
98
|
+
"MCP_API_KEY": "${input:nana800-api-key}"
|
|
78
99
|
}
|
|
79
100
|
}
|
|
80
101
|
}
|
|
81
102
|
}
|
|
82
103
|
```
|
|
83
104
|
|
|
84
|
-
|
|
105
|
+
### Other clients
|
|
106
|
+
|
|
107
|
+
Any MCP client that starts stdio servers works with the same command:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
MCP_API_KEY=your_api_key npx -y nana800-mcp-server
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
## ⚙️ Environment variables
|
|
85
114
|
|
|
86
115
|
| Variable | Required | Description |
|
|
87
116
|
|----------|----------|-------------|
|
|
88
|
-
| `MCP_API_KEY` | Yes | Your nana800.io API key |
|
|
89
|
-
| `MCP_PROJECT_ID` | No | Default project ID
|
|
90
|
-
| `MCP_SCHEME_ID` | No | Default scheme ID
|
|
117
|
+
| `MCP_API_KEY` | Yes | Your nana800.io API key from [cloud.nana800.io/settings](https://cloud.nana800.io/settings). The server stops with an error without it |
|
|
118
|
+
| `MCP_PROJECT_ID` | No | Default project ID for tools with an optional `project_id` |
|
|
119
|
+
| `MCP_SCHEME_ID` | No | Default scheme ID for tools with an optional `scheme_id` or `scheme` |
|
|
120
|
+
| `MCP_ANALYTICS_ORG_ID` | No | Default analytics org ID for tools with an optional `org_id`. Get it with `analytics_orgs_list` or from the `org` parameter of the analytics page URL |
|
|
91
121
|
| `MCP_API_URL` | No | API origin, `https://api.nana800.io` by default |
|
|
92
|
-
| `MCP_ANALYTICS_ORG_ID` | No | Default analytics org ID (can be overridden per tool call), get it with `analytics_orgs_list` or from the `org` parameter in the analytics page URL |
|
|
93
122
|
| `MCP_ANALYTICS_API_URL` | No | Analytics API origin, `https://api.analytics.nana800.io` by default |
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
| `
|
|
105
|
-
| `
|
|
106
|
-
| `
|
|
107
|
-
| `
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
| `
|
|
115
|
-
| `
|
|
116
|
-
| `
|
|
117
|
-
| `
|
|
118
|
-
| `
|
|
119
|
-
| `
|
|
120
|
-
| `
|
|
121
|
-
| `
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
| `
|
|
129
|
-
| `
|
|
130
|
-
| `
|
|
131
|
-
| `
|
|
132
|
-
| `
|
|
133
|
-
| `
|
|
134
|
-
| `
|
|
135
|
-
| `node_connect` | Connect two nodes
|
|
136
|
-
| `node_disconnect` |
|
|
123
|
+
| `MCP_CABINET_URL` | No | Web app origin used in chart and dashboard links, `https://cloud.nana800.io` by default |
|
|
124
|
+
|
|
125
|
+
An ID passed in a tool call always wins over the default. Every API request has a 30 second timeout.
|
|
126
|
+
|
|
127
|
+
## 🧰 Tools
|
|
128
|
+
|
|
129
|
+
### Projects
|
|
130
|
+
|
|
131
|
+
| Tool | What it does |
|
|
132
|
+
|------|--------------|
|
|
133
|
+
| `project_create` | Create a project, a container for schemes |
|
|
134
|
+
| `project_get` | Get a project by ID |
|
|
135
|
+
| `project_list_by_payment_account` | List projects of a payment account |
|
|
136
|
+
| `project_update` | Change project name or slug |
|
|
137
|
+
| `project_delete` | Delete a project with all its schemes (irreversible) |
|
|
138
|
+
|
|
139
|
+
### Schemes (workflows)
|
|
140
|
+
|
|
141
|
+
| Tool | What it does |
|
|
142
|
+
|------|--------------|
|
|
143
|
+
| `scheme_create` | Create a scheme in a project |
|
|
144
|
+
| `scheme_get` | Get a scheme by ID |
|
|
145
|
+
| `scheme_list_by_project` | List schemes of a project |
|
|
146
|
+
| `scheme_update` | Change name and description, enable or disable a scheme |
|
|
147
|
+
| `scheme_get_context_type` | Get the data type of the scheme context |
|
|
148
|
+
| `scheme_get_swagger_json` | Get the OpenAPI 3 document of the scheme webhooks: paths, methods, fields the blocks read, answers, and webhooks that get no requests with the reason |
|
|
149
|
+
| `scheme_export` | Export scheme nodes and connections as JSON |
|
|
150
|
+
| `scheme_import` | Import nodes into a scheme from exported JSON |
|
|
151
|
+
| `scheme_delete` | Delete a scheme with all its nodes (irreversible) |
|
|
152
|
+
|
|
153
|
+
### Nodes (blocks)
|
|
154
|
+
|
|
155
|
+
| Tool | What it does |
|
|
156
|
+
|------|--------------|
|
|
157
|
+
| `get_nodes_info` | List available trigger and action types with their config options, call it before creating nodes |
|
|
158
|
+
| `node_create_trigger` | Create a trigger node (for example `WEBHOOK`, `INTERVAL`) |
|
|
159
|
+
| `node_create_action` | Create an action node (HTTP request, email, integrations) |
|
|
160
|
+
| `node_get` | Get a node by ID |
|
|
161
|
+
| `node_list_by_scheme` | List nodes of a scheme |
|
|
162
|
+
| `node_update` | Change node slug or description |
|
|
163
|
+
| `node_update_config` | Change node configuration |
|
|
164
|
+
| `node_connect` | Connect two nodes, for condition nodes `connection_index` 0 is the "true" output and 1 is the "false" output |
|
|
165
|
+
| `node_disconnect` | Remove a connection between two nodes |
|
|
166
|
+
| `node_get_scheme_edges` | List all connections of a scheme |
|
|
167
|
+
| `node_find_existing_buttons` | List existing outputs of a node |
|
|
137
168
|
| `node_copy` | Copy a node |
|
|
138
|
-
| `
|
|
139
|
-
|
|
169
|
+
| `node_delete` | Delete a node (irreversible) |
|
|
170
|
+
|
|
171
|
+
### Run history
|
|
172
|
+
|
|
173
|
+
| Tool | What it does |
|
|
174
|
+
|------|--------------|
|
|
175
|
+
| `scheme_process_get` | Get one scheme run |
|
|
176
|
+
| `scheme_process_list_filtered` | List scheme runs by scheme or project, with status filters and pages |
|
|
177
|
+
| `scheme_process_delete` | Delete a scheme run record |
|
|
178
|
+
| `node_process_get` | Get one node run |
|
|
179
|
+
| `node_process_list_filtered` | List node runs by scheme, node or scheme run, with status filters and pages |
|
|
180
|
+
| `node_process_delete` | Delete a node run record |
|
|
140
181
|
|
|
141
|
-
###
|
|
182
|
+
### Payment account
|
|
142
183
|
|
|
143
|
-
| Tool |
|
|
144
|
-
|
|
145
|
-
| `
|
|
146
|
-
| `
|
|
147
|
-
| `
|
|
184
|
+
| Tool | What it does |
|
|
185
|
+
|------|--------------|
|
|
186
|
+
| `payment_account_get_by_user` | Get the payment account of a user |
|
|
187
|
+
| `payment_account_get_by_project` | Get the payment account of a project |
|
|
188
|
+
| `payment_account_update` | Change account name and automatic balance refill |
|
|
189
|
+
| `payment_account_get_transactions` | Get the transaction history |
|
|
190
|
+
| `payment_account_remove` | Remove the payment account from a user |
|
|
148
191
|
|
|
149
|
-
###
|
|
192
|
+
### Analytics: orgs, projects, events
|
|
150
193
|
|
|
151
|
-
| Tool |
|
|
152
|
-
|
|
153
|
-
| `
|
|
154
|
-
| `
|
|
155
|
-
| `
|
|
194
|
+
| Tool | What it does |
|
|
195
|
+
|------|--------------|
|
|
196
|
+
| `analytics_orgs_list` | List analytics orgs the API key owner is a member of |
|
|
197
|
+
| `analytics_projects_list` | List app projects of an analytics org |
|
|
198
|
+
| `analytics_event_types_list` | List tracked event types of an app project, for chart series and export filters |
|
|
199
|
+
| `analytics_event_properties_list` | List property keys of an event type, the most used first, for chart conditions and splits |
|
|
200
|
+
|
|
201
|
+
### Analytics charts
|
|
202
|
+
|
|
203
|
+
| Tool | What it does |
|
|
204
|
+
|------|--------------|
|
|
205
|
+
| `analytics_chart_preview` | Calculate a chart without saving it and return its numbers: totals per series, values per period, funnel steps, retention. Also takes `chart_id` of a saved chart |
|
|
206
|
+
| `analytics_chart_create` | Save a chart (`LINES_CHART`, `BARS`, `FUNNEL`, `RETENTION`) and return `chart_url`; `add_to_dashboard` puts it onto a dashboard in the same call |
|
|
207
|
+
| `analytics_chart_get` | Get a saved chart as an editable definition and its link |
|
|
208
|
+
| `analytics_chart_update` | Change a saved chart: name, series, period, metric, chart type, display settings |
|
|
209
|
+
| `analytics_chart_delete` | Delete a chart and remove it from every dashboard (irreversible) |
|
|
210
|
+
|
|
211
|
+
A chart is described the same way in `analytics_chart_preview`, `analytics_chart_create` and `analytics_chart_update`:
|
|
212
|
+
|
|
213
|
+
| Field | Meaning |
|
|
214
|
+
|-------|---------|
|
|
215
|
+
| `app_project_id` | Analytics project whose events are counted |
|
|
216
|
+
| `chart_variant` | `LINES_CHART` trend, `BARS` bars per period or one total bar per series, `FUNNEL` ordered steps, `RETENTION` start event + return event |
|
|
217
|
+
| `series` | `event_type_id`, `title` (label or funnel step name), `conditions` on event properties, `breakdown_property_key` to split by property values (lines and bars) |
|
|
218
|
+
| `common_conditions` | Conditions added to every series, for example to drop test traffic |
|
|
219
|
+
| `user_conditions` | Conditions on user properties for the whole chart |
|
|
220
|
+
| `metric` | `UNIQ_USERS` (default) or `TOTAL_EVENTS` |
|
|
221
|
+
| `period` | `time_scale` (`HOURLY`, `DAILY`, `WEEKLY`, `MONTHLY`) and `last_periods_count` for a live period (default last 30), or `from_time` + `to_time` for fixed dates |
|
|
222
|
+
| `funnel_conversion_window_seconds` | Funnel: all steps within this time from the first step |
|
|
223
|
+
| `retention_periods_count` | Retention: periods after the start period to track returns |
|
|
224
|
+
| `timezone_offset_minutes` | Day boundaries, minutes east of UTC (Moscow 180) |
|
|
225
|
+
| `display_settings` | `bars_mode` (`GROUPED`, `STACKED`, `TOTAL`), `value_mode`, renamed or colored series, up to 5 formulas like conversion = A / B |
|
|
226
|
+
|
|
227
|
+
The server writes the series where the web chart builder expects them, so every chart made through MCP opens and can be edited in the web app like a chart made by hand.
|
|
228
|
+
|
|
229
|
+
Example: "build a funnel from a view to a purchase for the last 30 days" becomes
|
|
230
|
+
|
|
231
|
+
```json
|
|
232
|
+
{
|
|
233
|
+
"chart_name": "Funnel: view → purchase",
|
|
234
|
+
"app_project_id": "<project id>",
|
|
235
|
+
"chart_variant": "FUNNEL",
|
|
236
|
+
"series": [
|
|
237
|
+
{ "event_type_id": "<id of page_viewed>", "title": "View" },
|
|
238
|
+
{ "event_type_id": "<id of checkout_started>", "title": "Checkout" },
|
|
239
|
+
{ "event_type_id": "<id of purchase_completed>", "title": "Purchase" }
|
|
240
|
+
],
|
|
241
|
+
"period": { "time_scale": "DAILY", "last_periods_count": 30 },
|
|
242
|
+
"funnel_conversion_window_seconds": 604800,
|
|
243
|
+
"add_to_dashboard": { "dashboard_id": "<dashboard id>", "width_size": 2 }
|
|
244
|
+
}
|
|
245
|
+
```
|
|
156
246
|
|
|
157
|
-
###
|
|
247
|
+
### Analytics dashboards
|
|
158
248
|
|
|
159
|
-
| Tool |
|
|
160
|
-
|
|
161
|
-
| `
|
|
162
|
-
| `
|
|
163
|
-
| `
|
|
164
|
-
| `
|
|
165
|
-
| `
|
|
249
|
+
| Tool | What it does |
|
|
250
|
+
|------|--------------|
|
|
251
|
+
| `analytics_dashboards_list` | List dashboards of an org with web app and public links |
|
|
252
|
+
| `analytics_dashboard_get` | Get a dashboard with its charts in order, widths and links |
|
|
253
|
+
| `analytics_dashboard_create` | Create an empty dashboard |
|
|
254
|
+
| `analytics_dashboard_update` | Rename a dashboard or change its description |
|
|
255
|
+
| `analytics_dashboard_add_chart` | Put a saved chart onto a dashboard at a position with a width, the charts below move down |
|
|
256
|
+
| `analytics_dashboard_set_chart_position` | Move a chart or change its width |
|
|
257
|
+
| `analytics_dashboard_remove_chart` | Take a chart off a dashboard, the chart stays saved |
|
|
258
|
+
| `analytics_dashboard_share_link` | Turn the public link on, reissue it (the old link stops working at once) or turn it off |
|
|
259
|
+
| `analytics_dashboard_delete` | Delete a dashboard, with `delete_charts` also its charts that are not on other dashboards (irreversible) |
|
|
166
260
|
|
|
167
|
-
|
|
261
|
+
A dashboard is a grid of 3 columns: `width_size` 1 is a third of a row, 2 is two thirds, 3 is the full row. Keep the sum of widths in a row equal to 3. The public link `https://cloud.nana800.io/share/dashboard/<token>` shows the charts without login, read only; turning it on needs the owner or editor role in the org.
|
|
168
262
|
|
|
169
|
-
|
|
263
|
+
### Analytics data export
|
|
170
264
|
|
|
171
|
-
| Tool |
|
|
172
|
-
|
|
173
|
-
| `analytics_orgs_list` | List analytics orgs the API key owner is a member of |
|
|
174
|
-
| `analytics_projects_list` | List app projects of an analytics org |
|
|
175
|
-
| `analytics_event_types_list` | List tracked event types of an app project, for export filters |
|
|
265
|
+
| Tool | What it does |
|
|
266
|
+
|------|--------------|
|
|
176
267
|
| `analytics_export_create` | Start an export of events (`EVENTS`), events of one user (`USER_EVENTS`) or users (`USERS`) to CSV or JSONL |
|
|
177
268
|
| `analytics_export_status` | Get export status (`QUEUED`, `RUNNING`, `DONE`, `FAILED`) and the download link when it is done |
|
|
178
269
|
| `analytics_exports_list` | List the 20 newest exports of an org |
|
|
179
270
|
|
|
271
|
+
The API key user must be a member of the analytics org. Exports run in the background and the tools return only the status and a download link, never the rows.
|
|
272
|
+
|
|
180
273
|
Export limits:
|
|
181
274
|
|
|
182
275
|
- Up to 1,000,000 rows per file, `is_truncated` is `true` when more rows matched
|
|
183
276
|
- One active export per org, 10 exports per org per hour, exports started with an API key: one per 10 minutes per org
|
|
184
|
-
- `time_from` and `time_to` are ISO 8601 date-times with a timezone,
|
|
277
|
+
- `time_from` and `time_to` are ISO 8601 date-times with a timezone, for example `2026-10-01T00:00:00.000Z`
|
|
185
278
|
- Poll `analytics_export_status` not more often than once per ~10 seconds
|
|
186
279
|
- The download link is valid for 15 minutes, call `analytics_export_status` again for a fresh one
|
|
187
280
|
- Files are deleted after 7 days
|
|
@@ -192,21 +285,41 @@ The file is served gzipped (`Content-Encoding: gzip`). A browser saves plain CSV
|
|
|
192
285
|
curl --compressed -o export.csv "<download_url>"
|
|
193
286
|
```
|
|
194
287
|
|
|
195
|
-
|
|
288
|
+
⚠️ Delete and remove tools can not be undone. Keep tool call confirmation on in your MCP client for them.
|
|
196
289
|
|
|
197
|
-
|
|
290
|
+
## 💬 Example prompts
|
|
198
291
|
|
|
199
|
-
- "List
|
|
200
|
-
- "Create a
|
|
201
|
-
- "Show
|
|
202
|
-
- "
|
|
203
|
-
- "
|
|
204
|
-
- "
|
|
292
|
+
- "List the schemes of my project and tell me which ones are disabled"
|
|
293
|
+
- "Create a scheme 'Lead to Telegram': a webhook trigger that sends the request body to my Telegram chat"
|
|
294
|
+
- "Show the nodes of scheme X and how they are connected"
|
|
295
|
+
- "Why did the last runs of scheme X fail? Look at the node runs"
|
|
296
|
+
- "Give me the OpenAPI document of scheme X and list the webhooks that get no requests"
|
|
297
|
+
- "Export scheme X as JSON and import its nodes into scheme Y"
|
|
298
|
+
- "Show the last transactions of my payment account"
|
|
205
299
|
- "Export all purchase events of the last week to CSV and give me the download link"
|
|
300
|
+
- "Build a funnel from a view to a purchase for the last 30 days"
|
|
301
|
+
- "Make a dashboard for my site: visitors per day, traffic channels and a funnel from a visit to a call, turn on the public link"
|
|
302
|
+
- "Which pages bring the most calls? Show it as total bars split by page"
|
|
303
|
+
|
|
304
|
+
## 🔗 Links
|
|
305
|
+
|
|
306
|
+
- Website: [nana800.io](https://nana800.io/en/)
|
|
307
|
+
- Web app: [cloud.nana800.io](https://cloud.nana800.io)
|
|
308
|
+
- Documentation: [nana800.gitbook.io/doc](https://nana800.gitbook.io/doc)
|
|
309
|
+
- Public API reference: [api.nana800.io/public-api](https://api.nana800.io/public-api)
|
|
310
|
+
- Privacy policy: [nana800_privacy.pdf](https://docs.nana800.io/nana800-files/service_documents/nana800_privacy.pdf)
|
|
311
|
+
- Telegram: [t.me/nana800_io](https://t.me/nana800_io)
|
|
312
|
+
|
|
313
|
+
## 🇷🇺 На русском
|
|
206
314
|
|
|
207
|
-
|
|
315
|
+
**nana800-mcp-server** - MCP-сервер для [nana800.io](https://nana800.io), no-code платформы для серверной логики и автоматизации. Через него ИИ-ассистент (Claude, Cursor, VS Code) создаёт проекты и схемы, добавляет и связывает блоки, смотрит историю запусков, данные платёжного аккаунта, строит графики и дашборды аналитики по просьбе словами и выгружает аналитику в CSV или JSON Lines.
|
|
208
316
|
|
|
209
|
-
|
|
317
|
+
- 🔑 Ключ API: [cloud.nana800.io/settings](https://cloud.nana800.io/settings), его нужно передать в переменной `MCP_API_KEY`
|
|
318
|
+
- 🚀 Запуск: `npx -y nana800-mcp-server`, готовые настройки для клиентов выше в разделе Quick start
|
|
319
|
+
- 🖥️ Сервер работает на вашем компьютере и ходит в API nana800 от имени владельца ключа
|
|
320
|
+
- 📈 Графики и дашборды: попросите, например, «построй воронку от просмотра до покупки за 30 дней» или «собери дашборд сайта из трёх графиков и включи публичную ссылку». Ассистент сам найдёт события, проверит цифры предпросмотром, сохранит графики, разложит их на дашборде и пришлёт ссылки на кабинет и публичную страницу
|
|
321
|
+
- ⚠️ Инструменты удаления (`project_delete`, `scheme_delete`, `node_delete` и другие) необратимы
|
|
322
|
+
- 📚 Документация: [nana800.gitbook.io/doc](https://nana800.gitbook.io/doc)
|
|
210
323
|
|
|
211
324
|
## License
|
|
212
325
|
|