Install and downloads

The packages are not yet published to PyPI or npm, and their source repository is not public yet. Until they are, everything they do is available over the HTTP API in the strategy contract; the SDKs add local checks and typed errors on top.

The SDKs and the MCP server are free to download and use under the Apache License 2.0. Using the Nevarn platform they call is licensed on the platform, by governed actions or by subscription.

The packages

Each package ships its LICENSE (Apache License 2.0) and a NOTICE naming Binaries Fort AB. The licence covers the package; using the platform it calls is licensed on the platform, by governed actions or by subscription.

Without a package: the HTTP API

Everything the SDKs and the MCP server do is a request to https://api.nevarn.com with your API key as a bearer token. The quickstart gets a first ruling with nothing but curl, and the strategy contract lists every route, field and error.

export NEVARN_API_KEY=nvk_…
curl -s https://api.nevarn.com/machine/mandate -H "Authorization: Bearer $NEVARN_API_KEY"

From a copy of the source

If you have a copy of the Nevarn source, these commands install the packages from it. Run them from the root of the copy. Each is a local install: nothing is fetched from a Nevarn registry, because there is none yet.

The Python SDK (Python 3.11 or later), into the environment your bot runs in:

python -m pip install ./apps/sdk/python
python -c "import nevarn; print(nevarn.VERSION)"   # 0.1.0

The TypeScript SDK and the MCP server (Node.js 20 or later). Install the two workspaces' dependencies, build them (building the server builds the SDK it uses), and pack each into a file your own project can install:

npm ci -w @nevarn/sdk -w @nevarn/mcp
npm run build -w @nevarn/mcp
npm pack -w @nevarn/sdk --pack-destination /path/to/your-bot
npm pack -w @nevarn/mcp --pack-destination /path/to/your-bot

cd /path/to/your-bot
npm install ./nevarn-sdk-0.1.0.tgz ./nevarn-mcp-0.1.0.tgz

Your project can then import { Client } from "@nevarn/sdk", and node_modules/.bin/nevarn-mcp is the MCP server. Install the two files together: the server depends on the SDK at the same version.

Check the install

• Python: nevarn.Client(baseUrl="https://api.nevarn.com") reads NEVARN_API_KEY and prints as Client(baseUrl='https://api.nevarn.com', apiKey=<redacted>).
• TypeScript: new Client({ baseUrl: "https://api.nevarn.com" }) reads NEVARN_API_KEY; JSON.stringify(client) shows only the base URL.
• MCP: started with NEVARN_BASE_URL and NEVARN_API_KEY set, nevarn-mcp logs a started line to stderr naming its seven tools. Without them, or given a session token, it exits with status 2.
• A key that is not an nvk_ key, or a base URL that is not https (plain http only on 127.0.0.1, localhost or [::1]), is refused before any request.

Next

• SDK usage: Python and TypeScript calls, errors and retries.
• MCP server setup: your client's configuration and the tool list.
• API keys and scopes: which key each call needs, and an execute key's limits.