nana800 MCP Server

Model Context Protocol (MCP) server for nana800.io, 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.

With this server an AI assistant (Claude, Cursor, VS Code and any other MCP client) works with your nana800 account through the Public API:

• 🧱 creates projects and schemes, adds trigger and action blocks, configures and connects them
• 📤 exports and imports schemes as JSON, reads the OpenAPI document of scheme webhooks
• 🔍 reads the run history of schemes and of single blocks
• 💳 reads the payment account and its transactions
• 📈 builds analytics charts and dashboards from a request in words: lines, bars, funnels, retention, splits by a property, filters, public dashboard links
• 📊 exports analytics events and users to CSV or JSON Lines files

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.

🔑 Get an API key

1. Sign in at cloud.nana800.io
2. Open cloud.nana800.io/settings and create or copy an API key
3. Put it into MCP_API_KEY in the client config below

The key acts as your user: the tools see and change only the projects your account has access to.

🚀 Quick start

Claude Desktop

Open Settings -> Developer -> Edit Config, or the file directly:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "nana800": {
      "command": "npx",
      "args": ["-y", "nana800-mcp-server"],
      "env": {
        "MCP_API_KEY": "your_api_key"
      }
    }
  }
}

Restart Claude Desktop after saving.

Claude Code

claude mcp add nana800 -e MCP_API_KEY=your_api_key -- npx -y nana800-mcp-server

Add --scope user to use it in all your projects.

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "nana800": {
      "command": "npx",
      "args": ["-y", "nana800-mcp-server"],
      "env": {
        "MCP_API_KEY": "your_api_key"
      }
    }
  }
}

VS Code

Add to .vscode/mcp.json. VS Code asks for the key on the first start and keeps it in its secret storage:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "nana800-api-key",
      "description": "nana800.io API key",
      "password": true
    }
  ],
  "servers": {
    "nana800": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "nana800-mcp-server"],
      "env": {
        "MCP_API_KEY": "${input:nana800-api-key}"
      }
    }
  }
}

Other clients

Any MCP client that starts stdio servers works with the same command:

MCP_API_KEY=your_api_key npx -y nana800-mcp-server

⚙️ Environment variables

Variable	Required	Description
MCP_API_KEY	Yes	Your nana800.io API key from cloud.nana800.io/settings. The server stops with an error without it
MCP_PROJECT_ID	No	Default project ID for tools with an optional project_id
MCP_SCHEME_ID	No	Default scheme ID for tools with an optional scheme_id or scheme
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
MCP_API_URL	No	API origin, https://api.nana800.io by default
MCP_ANALYTICS_API_URL	No	Analytics API origin, https://api.analytics.nana800.io by default
MCP_CABINET_URL	No	Web app origin used in chart and dashboard links, https://cloud.nana800.io by default

An ID passed in a tool call always wins over the default. Every API request has a 30 second timeout.

🧰 Tools

Projects

Tool	What it does
project_create	Create a project, a container for schemes
project_get	Get a project by ID
project_list_by_payment_account	List projects of a payment account
project_update	Change project name or slug
project_delete	Delete a project with all its schemes (irreversible)

Schemes (workflows)

Tool	What it does
scheme_create	Create a scheme in a project
scheme_get	Get a scheme by ID
scheme_list_by_project	List schemes of a project
scheme_update	Change name and description, enable or disable a scheme
scheme_get_context_type	Get the data type of the scheme context
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
scheme_export	Export scheme nodes and connections as JSON
scheme_import	Import nodes into a scheme from exported JSON
scheme_delete	Delete a scheme with all its nodes (irreversible)

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗