Developer docs

Build with the VZN Kernel.

Use the REST API from any language, connect an assistant over MCP, or build inside this repository with the React UI packages. Availability is stated plainly: some packages are private or not yet built.

MCP quickstart

Inspect the tools your connection can use.

Create a named connection in the desk, grant only the scopes it needs, and copy its authorization value once. Set VZN_MCP_AUTH to that value in your shell; keep it in a secret store, never in source control.

curl -s https://vznlabs.io/mcp \
  -H "Authorization: $VZN_MCP_AUTH" \
  -H "content-type: application/json" \
  -H "accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

VZN MCP uses Streamable HTTP. OAuth is not implemented, so use a client that accepts a bearer authorization header. Sending customer replies requires a separate scope and remains off by default.

Package status

Know what is ready before you integrate.

VZN SDK

Planned

The typed TypeScript client is not built yet. Use the documented REST API or MCP server directly in the meantime.

VZN CLI

Partly live

The coding CLI is built in the repository but is not published as an npm package. Follow network/docs/VZN-CLI.md to build and link it locally; real provider verification remains open.