_ registry / mcp streamable-http · checked 2h ago

neblla

https://neblla.com

Registry code: 1aea2aa3e559794e

api record

Build and publish multiplayer apps and games on Neblla: scaffold, edit files, ship to the gallery.

from a public catalogue that lists it, not from the operator

endpoint: https://neblla.com/mcp
protocol: streamable-http ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing
karma: 0 · newcomer

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

235ms

last good check

priced tools

of 28 tools

_ answered our checks, 90 days 1 checks · signed record

2026-09-26 18:36 unknown → live

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 28 tools

1 open1 auth-required 26 never probed 2 of 28 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

neblla_get_llms open 2h ago
Fetch the Neblla developer guide (llms.txt), split by topic so you read only what the app uses. Call this BEFORE designing or writing any code for a Neblla app — at minimum the `core` section (the default): the canonical six-file structure, the events-only client/server contract, and the five app patterns. Then fetch the sections matching the features you enabled: salas (rooms, lobby, matchmaking), servidor (the 3 server modes, setState, anti-cheat), identidad (login/SSO/scopes/save), social (friends + dev↔user communications), pagos (products/Stripe), ia (neblla.ai routes), publicar (gallery + quota table), referencia (the full API/events tables), mcp (this server's tools + creation flow), index (the table of contents), full (everything at once). Skipping core risks producing incorrect Neblla apps. Each response lists the available `sections`. Most sections fit in one response; for long ones check `hasMore` and re-call with `offset` = `nextOffset`, concatenating chunks in order. STALENESS CHECK — you connected to Neblla build 36. Each response carries the LIVE `latestBuild`. If `latestBuild` is greater than 36 (the build noted here), the server was redeployed AFTER you connected, so your loaded Neblla tool list is STALE. In that case, tell the developer plainly: "⚠️ The Neblla MCP updated to build <latestBuild> since this session started (you are on build 36). Restart/reconnect Claude Code to get the latest tools."

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "offset": { "type": "integer", "default": 0, "minimum": 0, "description": "Character position to start reading from. 0 = start. Pass the previous response's `nextOffset` for the next chunk." }, "section": { "enum": [ "index", "full", "core", "salas", "servidor", "identidad", "social", "pagos", "ia", "publicar", "referencia", "mcp" ], "type": "string", "default": "core", "description": "Which part of the guide to read. Default \"core\" — the mandatory contract. \"index\" = table of contents, \"full\" = the whole guide." }, "maxLength": { "type": "integer", "default": 20000, "maximum": 65536, "minimum": 1024, "description": "Maximum length of `guide` to return in this chunk. The default stays under the response-size limit of MCP clients." } }, "additionalProperties": false }
arguments 39 lines
neblla_list_apps auth-required 2h ago
List all apps owned by the authenticated developer.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
neblla_upload_file unknown never probed
Upload or update a file for an app. Pass text files (HTML, CSS, JS, TS, JSON, SVG) as raw UTF-8 text with encoding="utf8" (the default) — do NOT base64-encode them, even if they contain quotes, backticks, ${...} or newlines; send the source verbatim. For binary files (images, fonts, audio, video) you have TWO options: (a) pass a public URL via `contentUrl` — Neblla downloads the bytes server-side (recommended: no need to spend tokens base64-encoding the file in this conversation), OR (b) pass a base64 string via `content` with encoding="base64". Always prefer `contentUrl` when you have one. Uploading the same path again overwrites the previous version. Canonical paths for a Neblla app are index.html, main.css, client.js (front-end) plus server/lobby.js, server/gathering.js, server/room.js (server-side). The server/ files are special: the SDK loads them itself and runs them in an isolated scope with no DOM access — never reference them from index.html, and never put DOM code or window.onNeblla in them (they must be top-level code where `neblla` is in scope as a global). client.js, by contrast, uses window.onNeblla = (neblla) => {…}. Communication between client.js and the server files is events-only (sendMessage / tellPresenter / tellServer / messageToServer / messageFromServer / setState / on('message')) — never direct function calls. All three server/ files run on the room's SERVER PEER (a device the SDK picks, never the presenter): server/lobby.js for the lobby (matchmaking); server/gathering.js while a non-lobby room is in 'gathering' state (decide when to call neblla.startRoom() to start the game); server/room.js post-startRoom (authoritative game logic — handle messageToServer, broadcast with sendMessage / setState).

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appId", "path" ], "properties": { "path": { "type": "string", "description": "File path within the app. Canonical: \"index.html\", \"main.css\", \"client.js\", \"server.js\". Subfolders allowed for assets." }, "appId": { "type": "string", "description": "The app public ID" }, "content": { "type": "string", "description": "File content. For text files: the raw source as-is (NOT base64). For binary files: a base64 string. Required UNLESS `contentUrl` is set." }, "encoding": { "enum": [ "utf8", "base64" ], "type": "string", "default": "utf8", "description": "Content encoding for `content`. Ignored when `contentUrl` is used. Use \"utf8\" for all text files (HTML/CSS/JS/TS/JSON/SVG); \"base64\" only for binary assets." }, "contentUrl": { "type": "string", "description": "Public URL of the file to upload. Neblla downloads it server-side (no need to base64-encode in this conversation). Use this for any binary asset (images, fonts, audio, video) when you have a URL. Mutually exclusive with `content`." } }, "additionalProperties": false }
arguments 36 lines

neblla_delete_file unknown never probed

Delete a single file from an app.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "File path to delete, e.g. \"old-page.html\""
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    }
  },
  "additionalProperties": false
}

arguments 19 lines

neblla_update_product unknown never probed

Update an existing product. Pass only the fields to change. Use this to adjust price, rename, or republish a product without losing its productId — changing the id would break checkout flows already wired into the app.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "productId"
  ],
  "properties": {
    "max": {
      "type": "number",
      "description": "Maximum quantity for consumable"
    },
    "min": {
      "type": "number",
      "description": "Minimum quantity for consumable"
    },
    "name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "additionalProperties": {
            "type": "string"
          }
        }
      ],
      "description": "Product name, string or { en: \"...\", es: \"...\" }"
    },
    "step": {
      "type": "number",
      "description": "Quantity step for consumable selector"
    },
    "image": {
      "type": "string",
      "description": "Product image URL"
    },
    "price": {
      "type": "number",
      "description": "Price in cents (one_time)"
    },
    "currency": {
      "type": "string",
      "description": "ISO 4217 code, e.g. \"usd\""
    },
    "productId": {
      "type": "string",
      "description": "The product ID returned by neblla_create_product"
    },
    "published": {
      "type": "boolean",
      "description": "Whether the product is buyable"
    },
    "defaultLang": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "it",
        "pt",
        "ja",
        "ko",
        "zh",
        "ar"
      ],
      "type": "string"
    },
    "description": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "additionalProperties": {
            "type": "string"
          }
        }
      ],
      "description": "Description, string or per-language object"
    },
    "pricePerUnit": {
      "type": "number",
      "description": "Price per unit in cents (consumable)"
    }
  },
  "additionalProperties": false
}

arguments 89 lines

neblla_unpublish_app unknown never probed

Remove an app from the public gallery. The app keeps its files and URL — only its public listing is hidden. Use neblla_publish_app to re-publish.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    }
  },
  "additionalProperties": false
}

arguments 14 lines

neblla_delete_communication unknown never probed

Permanently remove a communication from a user's thread. The end user is notified via a `communicationDeleted` socket event so their UI updates in real time.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userId",
    "commId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "commId": {
      "type": "string",
      "description": "Communication id to delete"
    },
    "userId": {
      "type": "string",
      "description": "User's mongo ObjectId hex string"
    }
  },
  "additionalProperties": false
}

arguments 24 lines

neblla_delete_account unknown never probed
For safety the MCP never deletes accounts directly. Returns a URL for the user to visit and confirm deletion from the Neblla dashboard.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
neblla_get_app_url unknown never probed
Returns the canonical public URL for a Neblla app in the gallery. ALWAYS call this after neblla_create_app — never construct the URL yourself. Apps are published and browsed at play.neblla.com. The URL format is https://play.neblla.com/<slug>, where <slug> is auto-generated from the app name at creation time and can be renamed in the dashboard.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appId" ], "properties": { "appId": { "type": "string", "description": "The app public ID" } }, "additionalProperties": false }
arguments 14 lines
neblla_validate_requirements unknown never probed
Walk the SAME decision map the Neblla dashboard wizard uses, before creating an app. STRONGLY RECOMMENDED before neblla_create_app on any new-app request (skip it only for edits/fixes to existing code). It front-loads every structural decision so the app is born configured right. How to use it: pass the `decisions` you can already answer from the user's request. The tool returns every still-pending decision, each with `how_to_infer` (how to answer it YOURSELF from context) and `ask_user` (whether it deserves a question to the human). The contract: ANSWER EVERY DECISION YOU CAN YOURSELF — only surface the ones in `ask_user_questions` to the user, and only when you genuinely cannot infer them; ask them all in ONE message. Then call this tool again with the full set. When `have_enough_context` is true, pass the returned `decisions` straight to neblla_create_app({ name, decisions }) — it scaffolds the matching pattern + themed UI pieces and writes the app config in one go. `plan` previews exactly what that will build. Decision ids: kind (game|app), players (single|lobby-only|multi — single = one device; lobby-only = everyone in one shared space with no separate rooms; multi = separate rooms), structure (turn-based|host-controllers|collab-realtime; multi only), login/friends/purchases/ai/communications (booleans — the feature pieces), connections (all|p2p|server), serverMode (js|wasm), roomsPolicy (ephemeral|public|private|mixed), matchmakingMode (nocode|custom), aiPayer (off|browser|server; when ai is on), palette ({primary, secondary, alert} hex colors — PICK THEM YOURSELF to match the app's character), typography (modern|editorial|techy|serif|playful — pick it yourself too).

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "decisions": { "type": "object", "default": {}, "description": "Decisions answered so far, keyed by decision id. Example: { kind: \"game\", players: \"multi\", structure: \"turn-based\", login: true, palette: { primary: \"#0F7BD7\", secondary: \"#15C2B0\", alert: \"#FF8552\" }, typography: \"techy\" }. Include everything the user stated plus everything you inferred.", "additionalProperties": {} } }, "additionalProperties": false }
arguments 13 lines

neblla_create_app unknown never probed

Create a new Neblla app. Returns the app ID (appId) to use in subsequent file upload operations. Recommended flow for a NEW app: 1) Call neblla_validate_requirements with the decisions you can infer from the request — it walks the same decision map as the dashboard wizard; answer what you can yourself, ask the user only what it flags, repeat until have_enough_context. 2) Call neblla_get_llms to read the SDK reference (the core section at minimum). 3) Call neblla_create_app (this tool) with the display name AND the validated `decisions` — that scaffolds the matching pattern with a themed UI piece per enabled feature (login, store, AI box, friends, inbox…) and writes the full app config, so you only EDIT files instead of writing from scratch. Omit `decisions` only if you genuinely want a blank app (just index.html). 4) Edit/replace the scaffolded files (or upload new ones). The server-side files live under server/ — index.html references only main.css and client.js (NEVER the server/ files — the SDK loads them); client.js wraps code in window.onNeblla; the server/ files are top-level code with no DOM access; client and server communicate only via events (tellServer / tellPresenter / sendMessage / setState / on('messageToServer'|'messageFromServer'|'message'|'state')). 5) Call neblla_get_app_url(appId) to get the correct public URL — NEVER construct it manually. Apps are served at play.neblla.com/<slug>, not under any /apps/ path.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "minLength": 1,
      "description": "Display name for the app"
    },
    "template": {
      "enum": [
        "turn-based",
        "host-controllers",
        "collab-realtime",
        "solo-save"
      ],
      "type": "string",
      "description": "Legacy alternative to `decisions`: scaffold the six canonical files wired to this pattern, with no feature pieces and no theme. Prefer `decisions`. Omit both for a blank app."
    },
    "decisions": {
      "type": "object",
      "description": "The COMPLETE decision set from neblla_validate_requirements (have_enough_context: true → pass its `decisions` verbatim). Scaffolds the matching pattern with the themed UI pieces for each enabled feature AND writes the app config (features, connections, serverMode, rooms policy, matchmaking mode, AI payer, theme). The recommended way to create any non-blank app.",
      "additionalProperties": {}
    },
    "serverMode": {
      "enum": [
        "js",
        "wasm",
        "infra"
      ],
      "type": "string",
      "description": "Where the server/ files run: \"js\" (default — plain JS on a connected peer), \"wasm\" (AssemblyScript .ts → WASM on a peer, opaque to DevTools), or \"infra\" (JS on a Neblla worker per room — Beta — for ranked/real-money). The template is scaffolded in JS for \"js\"/\"infra\" and in AssemblyScript for \"wasm\". Most apps want \"js\". With `decisions`, omit — it is derived."
    }
  },
  "additionalProperties": false
}

arguments 39 lines

neblla_delete_app unknown never probed

Permanently delete an app and all its files.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    }
  },
  "additionalProperties": false
}

arguments 14 lines

neblla_update_app unknown never probed

Update an app's configuration. Pass only the fields you want to change. Use addDomain/removeDomain to mutate the allowed-origins list atomically without overwriting other entries. `sandbox: true` lets the app load on localhost / non-https origins for development. `ai` is the AI proxy config for the SDK's neblla.ai() — set { model, maxOutputTokens, userTokenMode, presets, limitsEnabled, tokensPerDay } or null to disable. userTokenMode is one of: 'off' (server uses dev key only), 'browser' (user key, browser-direct), 'server' (user key, server-side with private preset prefixes). presets is a {name: prefix} map of named prompt prefixes invoked via neblla.ai({preset:'name'}). limitsEnabled + tokensPerDay cap how many Claude tokens each end-user can spend per day; only applied when userTokenMode = off. `inbox: true` enables the in-app communications inbox feature for end users.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "ai": {
      "anyOf": [
        {
          "type": "object",
          "properties": {},
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "description": "AI proxy config: { model, maxOutputTokens, userTokenMode, presets, limitsEnabled, tokensPerDay } — pass null to disable"
    },
    "name": {
      "type": "string",
      "description": "New display name"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "inbox": {
      "type": "boolean",
      "description": "Enable/disable in-app communications inbox for end users"
    },
    "sandbox": {
      "type": "boolean",
      "description": "Allow non-https / localhost loads for development"
    },
    "addDomain": {
      "type": "string",
      "description": "Append a domain entry (URL or origin) to the allowed list"
    },
    "matchmaking": {
      "anyOf": [
        {
          "type": "object",
          "properties": {},
          "additionalProperties": true
        },
        {
          "type": "null"
        }
      ],
      "description": "No-code matchmaking config: { mode: \"nocode\"|\"custom\", rule: \"count\"|\"timer\"|\"count_then_timer\"|\"button\", minPlayers, maxPlayers (0=unlimited), waitSeconds, allowPresenterStart }. In \"nocode\" mode this regenerates server/gathering.js from the rules; in \"custom\" mode you own that file."
    },
    "removeDomain": {
      "type": "string",
      "description": "Remove a domain entry exactly matching this string"
    }
  },
  "additionalProperties": false
}

arguments 60 lines

neblla_list_files unknown never probed

List all files staged for an app. Returns path, mimeType, size, and timestamps for each file.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    }
  },
  "additionalProperties": false
}

arguments 14 lines

neblla_get_file unknown never probed

Get the content of a specific file. Text files (HTML, CSS, JS, JSON, SVG, plain text) are ALWAYS returned as UTF-8 strings — never base64. Binary files (images, fonts, audio) are returned as base64. The response includes an `encoding` field ("utf8" or "base64") so you know how to interpret `content`. Always returns the real current source, including for apps you created or published in a previous session. Use this to resume editing an existing app across sessions. Large files are returned in CHUNKS — `content` may be only PART of the file. After each call, check `hasMore`: if true, call this tool again with `offset` set to the returned `nextOffset`, then concatenate the chunks in order. Decode (for binary) or edit only the FULLY reassembled string. `totalLength` is the total length of `content` across all chunks; `length` is this chunk's length.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "path"
  ],
  "properties": {
    "path": {
      "type": "string",
      "description": "File path, e.g. \"index.html\""
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Where to start reading, in units of the returned `content` (characters for utf8 text, base64 characters for binary). 0 = start of file. Pass the previous response's `nextOffset` to get the next chunk."
    },
    "maxLength": {
      "type": "integer",
      "default": 20000,
      "maximum": 65536,
      "minimum": 1024,
      "description": "Maximum length of `content` to return in this chunk. The default (20000) stays comfortably under the response-size limit of MCP clients; lower it further if your client still truncates the reply."
    }
  },
  "additionalProperties": false
}

arguments 32 lines

neblla_move_file unknown never probed

Rename or move a file within an app. oldPath is the current path, newPath is the destination.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "oldPath",
    "newPath"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "newPath": {
      "type": "string",
      "description": "New file path, e.g. \"new-name.html\" or \"subfolder/file.html\""
    },
    "oldPath": {
      "type": "string",
      "description": "Current file path, e.g. \"old-name.html\""
    }
  },
  "additionalProperties": false
}

arguments 24 lines

neblla_create_product unknown never probed

Create a purchasable product for a Neblla app. type must be "one_time" (single purchase, fixed price) or "consumable" (quantity selector, price per unit). name should be a multi-language object e.g. { en: "Gold Coins", es: "Monedas de Oro" }. price (one_time) and pricePerUnit (consumable) are in cents (e.g. 499 = $4.99).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "name",
    "type"
  ],
  "properties": {
    "max": {
      "type": "number",
      "description": "Maximum quantity for consumable"
    },
    "min": {
      "type": "number",
      "description": "Minimum quantity for consumable"
    },
    "name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "object",
          "additionalProperties": {
            "type": "string"
          }
        }
      ],
      "description": "Product name, string or { en: \"...\", es: \"...\" }"
    },
    "step": {
      "type": "number",
      "description": "Quantity step for consumable selector"
    },
    "type": {
      "enum": [
        "one_time",
        "consumable"
      ],
      "type": "string"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "image": {
      "type": "string",
      "description": "Product image URL"
    },
    "price": {
      "type": "number",
      "description": "Price in cents — required for one_time"
    },
    "pricePerUnit": {
      "type": "number",
      "description": "Price per unit in cents — required for consumable"
    }
  },
  "additionalProperties": false
}

arguments 61 lines

neblla_list_products unknown never probed

List all products for a Neblla app.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    }
  },
  "additionalProperties": false
}

arguments 14 lines

neblla_delete_product unknown never probed

Permanently delete a product from a Neblla app.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "productId"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "description": "The product ID returned by neblla_create_product"
    }
  },
  "additionalProperties": false
}

arguments 14 lines

neblla_publish_app unknown never probed

Publish a Neblla app to the public gallery. BEFORE calling this tool you MUST follow these steps with the user: 1) Ask for the app title and a short description (1-3 sentences) in the user's language. 2) Ask for the gallery section: "multiplayer" (games/apps where users interact in real time), "singleplayer" (games/tools for one person at a time), or "app" (everything else — utilities, tools, sites). 3) Ask for tags that describe the app (e.g. "puzzle", "multiplayer", "drawing"). 4) Ask what devices the app is best suited for: "mobile", "desktop", or omit for both. 5) Ask if the user wants to upload a cover image — pass an http(s) URL, a data: URI, or raw base64 JPEG/PNG. It will be auto-scaled to 400x400. 6) Provide the title and description in at least the user's language. You SHOULD also translate into other supported languages (en, es, fr, de, it, pt, ja, ko, zh, ar) for wider reach, but only the original language is required. Set defaultLang to the language the user originally provided the content in. titles and descriptions MUST each contain at least one entry in the same language.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "section",
    "titles",
    "descriptions"
  ],
  "properties": {
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags describing the app"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "bestOn": {
      "enum": [
        "mobile",
        "desktop"
      ],
      "type": "string",
      "description": "Device the app is best suited for. Omit for both mobile and desktop."
    },
    "titles": {
      "type": "object",
      "description": "Title per language code, e.g. { en: \"My App\", es: \"Mi App\" }. At least one entry required.",
      "additionalProperties": {
        "type": "string"
      }
    },
    "section": {
      "enum": [
        "singleplayer",
        "multiplayer",
        "app"
      ],
      "type": "string",
      "description": "Gallery section: \"multiplayer\" (real-time/social), \"singleplayer\" (one player at a time), or \"app\" (utilities/tools/sites)"
    },
    "portrait": {
      "type": "string",
      "maxLength": 262144,
      "description": "Cover image. Accepts an http(s) URL, a data: URI, or raw base64 (JPEG/PNG/GIF/BMP/TIFF). Auto-scaled to 400x400 JPEG, stored as portrait.jpg, and set as cover_image."
    },
    "defaultLang": {
      "enum": [
        "en",
        "es",
        "fr",
        "de",
        "it",
        "pt",
        "ja",
        "ko",
        "zh",
        "ar"
      ],
      "type": "string",
      "default": "en"
    },
    "descriptions": {
      "type": "object",
      "description": "Description per language code (max 500 chars each). At least one entry required.",
      "additionalProperties": {
        "type": "string"
      }
    }
  },
  "additionalProperties": false
}

arguments 76 lines

neblla_set_communication_read unknown never probed

Mark a specific communication as read or unread (from the developer's side). The end user is notified live via a `communicationRead` socket event if connected.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userId",
    "commId"
  ],
  "properties": {
    "read": {
      "type": "boolean",
      "default": true
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "commId": {
      "type": "string",
      "description": "Communication id (the ISO timestamp returned when the message was created)"
    },
    "userId": {
      "type": "string",
      "description": "User's mongo ObjectId hex string"
    }
  },
  "additionalProperties": false
}

arguments 28 lines

neblla_set_communication_important unknown never probed

Toggle the "important" flag on a communication. This is dev-only metadata and is NOT broadcast to the end user — use it to bubble messages to the top of your own triage view.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userId",
    "commId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "commId": {
      "type": "string",
      "description": "Communication id"
    },
    "userId": {
      "type": "string",
      "description": "User's mongo ObjectId hex string"
    },
    "important": {
      "type": "boolean",
      "default": true
    }
  },
  "additionalProperties": false
}

arguments 28 lines

neblla_update_user_data unknown never probed
Replace the `data` object for a specific end user (the same object the SDK's neblla.save() reads/writes). Use sparingly: this overwrites the user's saved state and the change is broadcast live. Useful for support (unstuck a player), moderation (clear a corrupted save), or admin tooling. If the app has a "bring your own database" target configured, this writes there. Mongo-reserved keys (starting with $ or containing ".") are rejected; total JSON size is capped at ~100KB and 10 levels deep.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "appId", "userId", "data" ], "properties": { "data": { "type": "object", "description": "The replacement data object (must be a plain object, not array/null)", "additionalProperties": {} }, "appId": { "type": "string", "description": "The app public ID" }, "userId": { "type": "string", "description": "User's mongo ObjectId hex string" } }, "additionalProperties": false }
arguments 25 lines

neblla_list_users unknown never probed

List end users of an app — the people who connected through the SDK, NOT the developer's own account. Use this as the entry point for the backoffice flow: it returns a paginated list with each user's mongo `_id` (needed for every other backoffice tool), email, name, language, and stats. Pass `withCommunicationsOnly: true` to get only users who have communication threads — useful when triaging support.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "skip": {
      "type": "integer",
      "default": 0,
      "minimum": 0
    },
    "sort": {
      "enum": [
        "date_desc",
        "date_asc",
        "email_asc",
        "email_desc"
      ],
      "type": "string",
      "default": "date_desc"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 100,
      "minimum": 1
    },
    "emailFilter": {
      "type": "string",
      "description": "Substring match against the user's email (case-insensitive). Ignored if withCommunicationsOnly is true."
    },
    "withCommunicationsOnly": {
      "type": "boolean",
      "default": false,
      "description": "Only return users with a non-empty communications array"
    }
  },
  "additionalProperties": false
}

arguments 44 lines

neblla_search_users_by_email unknown never probed

Find users of an app by a partial email match (min 2 characters). Returns the matching user docs with email, communications, data, stats, and language. Use neblla_list_users for full pagination instead when no email is known.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "emailPart"
  ],
  "properties": {
    "skip": {
      "type": "integer",
      "default": 0,
      "minimum": 0
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 50,
      "minimum": 1
    },
    "emailPart": {
      "type": "string",
      "minLength": 2,
      "description": "At least 2 characters of the email to match"
    }
  },
  "additionalProperties": false
}

arguments 31 lines

neblla_get_user unknown never probed

Fetch the full record of a single end user — their saved data, public info, purchases, and communications thread. Use the `_id` from neblla_list_users / neblla_search_users_by_email as `userId`.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userId"
  ],
  "properties": {
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "userId": {
      "type": "string",
      "description": "The user's mongo ObjectId hex string (the `_id` returned by neblla_list_users)"
    }
  },
  "additionalProperties": false
}

arguments 19 lines

neblla_list_communications unknown never probed

List communications across ALL users of an app, filtered and sorted. The most useful tool for triaging an inbox: show only unread, only messages from users (not the dev), only flagged-important, or only those mentioning a given email. Returns flat items with userId so you can follow up via neblla_send_communication on each thread.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId"
  ],
  "properties": {
    "skip": {
      "type": "integer",
      "default": 0,
      "minimum": 0
    },
    "sort": {
      "enum": [
        "date_desc",
        "date_asc",
        "email_asc",
        "email_desc"
      ],
      "type": "string",
      "default": "date_desc"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "limit": {
      "type": "integer",
      "default": 50,
      "maximum": 200,
      "minimum": 1
    },
    "fromFilter": {
      "enum": [
        "all",
        "user",
        "dev"
      ],
      "type": "string",
      "default": "all",
      "description": "\"user\" = sent by end-user, \"dev\" = sent by you, \"all\" = both"
    },
    "readFilter": {
      "enum": [
        "all",
        "read",
        "unread"
      ],
      "type": "string",
      "default": "all"
    },
    "emailFilter": {
      "type": "string",
      "description": "Case-insensitive email substring filter"
    },
    "importantOnly": {
      "type": "boolean",
      "default": false
    }
  },
  "additionalProperties": false
}

arguments 62 lines

neblla_send_communication unknown never probed

Send a message from the developer to a specific end user. The user receives it live via the SDK's `communicationUpdated` event if connected, and on next reconnect otherwise. Optionally attach a `data` JSON payload (rendered by the app), or a calendar/appointment proposal via dateFrom/dateTo. Set `thread` to the id of an earlier communication to group replies. BEFORE calling: confirm the message wording with the developer (you are speaking to their users on their behalf).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "appId",
    "userId",
    "message"
  ],
  "properties": {
    "data": {
      "description": "Optional JSON payload attached to the communication"
    },
    "appId": {
      "type": "string",
      "description": "The app public ID"
    },
    "dateTo": {
      "type": "string",
      "description": "Optional calendar/appointment proposal end (ISO 8601)"
    },
    "thread": {
      "type": "string",
      "description": "Id of the parent communication to thread under"
    },
    "userId": {
      "type": "string",
      "description": "Target user's mongo ObjectId hex string"
    },
    "message": {
      "type": "string",
      "minLength": 1,
      "description": "Plain-text message body"
    },
    "dateFrom": {
      "type": "string",
      "description": "Optional calendar/appointment proposal start (ISO 8601)"
    }
  },
  "additionalProperties": false
}

arguments 40 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/1aea2aa3e559794e/badge.svg)](https://brick.blue/agent/1aea2aa3e559794e)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.