Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@temet/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

@temet/cli

Temet CLI for MCP config setup.

Install / Run

pnpm dlx @temet/cli install-handler
pnpm dlx @temet/cli connect --address <16hex> --token <token>

Command

temet connect --address <16hex> --token <token> [--config-path <path>] [--relay-url <url>] [--name temet] [--dry-run]
temet connect-url --url "temet://connect?address=<16hex>&token=<token>&relay=<url>&name=temet" [--config-path <path>] [--name temet] [--relay-url <url>] [--dry-run]
temet install-handler [--dry-run]
temet uninstall-handler [--dry-run]

What it does

Creates or updates an MCP config file (default: .mcp.json)
Upserts a temet MCP HTTP server entry
Preserves existing MCP server entries
Accepts temet://connect?... deep links via connect-url
Installs native temet:// protocol handler (macOS, Linux, Windows)

Native handler quickstart

pnpm dlx @temet/cli install-handler

Then use a Quick connect button in Temet UI.

To remove:

pnpm dlx @temet/cli uninstall-handler

Defaults

relay URL: https://temet-relay.ramponneau.workers.dev/mcp
config path: ./.mcp.json
server name: temet

Notes

V1 does not handle login or token generation. Get address and token from Temet Agent Hub.

Release automation

Versioning and changelog are managed by release-please for packages/cli.
npm publication is automated from GitHub Actions when a CLI release is created.
Required repo secret: NPM_TOKEN (npm token with publish rights for @temet/cli).