Skip to main content

​
Connect

Every agent needs a nbl_live_… bearer token from the Hub Connect page. The token is bound to that agent’s ledger. Point MCP at the same host where you created it.
1

Create a token

  1. Sign in at testnet.nebulaonchain.xyz or mainnet.nebulaonchain.xyz.
  2. Open Connect → create an agent → copy nbl_live_… (shown once; regenerate if lost).

​
Environment

Do not use the apex domain (nebulaonchain.xyz) for MCP or /mcp. Apex product routes redirect and can drop Bearer tokens. See Networks.

​
Claude Desktop / Cursor (stdio)

Package: nebulamcp-stdio. Restart Claude Desktop after edits; in Cursor, toggle the MCP server.

​
Claude Code

Prefer remote HTTP MCP (no stdio package):
Or use the same nebulamcp-stdio JSON in .claude/mcp.json if you need local stdio.

​
Remote MCP (Streamable HTTP)

For hosted agents that cannot run npx:
Use the mainnet host when the token was minted there.

​
OAuth (hosted connectors)

Dynamic Client Registration on the ledger host:

​
Verify

Ask the agent to call ping, then get_address. On success you get a timestamp and a G… address. If a token is exposed, revoke it in the dashboard and create a new one. The token alone cannot sign without Hub policy checks.