MCP Server

Connect an AI agent to NxCreator over MCP to authenticate, create bots, read and edit code, deploy, restart, and read logs.

The NxCreator MCP server lets an AI agent (Claude Desktop, Cursor, Claude Code, or your own client) authenticate with your API key and operate directly on your bots — create them, read and edit their code, deploy, restart, and pull logs. Edits apply immediately and restart the bot; there is no review step.

Endpoint

One HTTP endpoint, JSON-RPC 2.0 over MCP Streamable HTTP:

https://nxcreate.com/api/mcp/project

Authentication

Every request must send your personal API key as a bearer token:

Authorization: Bearer <your API key>

Find your key in the dashboard under Settings → Account → API Key. It is created on first visit and stays stable until you regenerate it.

Your API key grants full access to your bots and account. Treat it like a password — never commit it or expose it in client-side code.

Client Setup

Add the server to your MCP client config. For Claude Desktop / Claude Code / Cursor:

{
  "mcpServers": {
    "nxcreate": {
      "url": "https://nxcreate.com/api/mcp/project",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

For a manual JSON-RPC call:

curl -X POST https://nxcreate.com/api/mcp/project \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"list_bots","arguments":{}}}'

Available Tools

Bots

Tool	Description
`get_dev_guide`	Returns the NxCreator bot development guide. Call this first — it teaches the agent the runtime rules so generated code is compatible.
`whoami`	Verify the API key; returns account email, uid, plan, and bot count.
`list_bots`	List the bots on your account with id, token status, framework, plan, and last update.
`create_bot`	Create a bot. Requires a @BotFather token; initial code is optional.
`get_bot_code`	Read the full bot source, split into named sections.
`update_section`	Replace one section (by uuid) or the whole file. Syntax-checked, applied immediately, bot restarted.
`update_bot_code`	Replace all of a bot's code with new source. Syntax-checked, applied immediately, bot restarted.
`restart_bot`	Restart a running bot.
`set_bot_token`	Set or replace a bot's @BotFather token.
`deploy_bot`	Deploy / activate a bot (set webhook + start). Can set the token first.
`get_bot_logs`	Fetch recent runtime logs, newest first (limit 1–200).

Mini Apps

Mini Apps are single hosted .html pages, not JavaScript modules — provide a complete HTML document.

Tool	Description
`list_mini_apps`	List your Mini Apps with id, name, hosted URL, and status.
`create_mini_app`	Create a Mini App. Optionally pass the full HTML to publish it on creation.
`get_mini_app_html`	Fetch the current published HTML of a Mini App.
`update_mini_app_html`	Replace and publish a Mini App's HTML. Provide a complete HTML document.
`delete_mini_app`	Delete a Mini App.

Standard MCP methods initialize, tools/list, and ping are also supported.

Recommended Workflow

Step	Call
1. Learn the runtime	`get_dev_guide`
2. Confirm the key	`whoami`
3. Find or create a bot	list_bots` → `create_bot
4. Read current code	`get_bot_code`
5. Make the change	update_section` or `update_bot_code
6. Verify	`get_bot_logs`

Edits apply immediately with no review step, so verify each change: new code is syntax-checked before it is written (a syntax error is rejected and the running bot is left untouched), and after a successful edit the bot restarts — call get_bot_logs to confirm the runtime reloaded without errors. Use a section uuid with update_section for a targeted change, or omit it to replace the whole file.

Last updated August 11, 2026

Was this page helpful?