{ "extensions": { "edisyl-docs": { "enabled": true, "name": "edisyl-docs", "type": "streamable_http", "uri": "https://docs.edisyl.com/mcp", "envs": {}, "env_keys": [], "headers": {}, "description": "", "timeout": 300, "bundled": null, "available_tools": [] } } }

Install & log in

The CLI targets the dev environment by default, so getting started is just an install and a login.

Install the CLI.

curl -fsSL https://cli.dev.edisyl.com/install.sh | sh

Log in.
Terminal window
```
edisyl login
```
This authenticates against dev via OAuth (or a pasted API key).
Confirm who and where you are.
Terminal window
```
edisyl whoami
```
This prints your user and workspace. The workspace (org) is already provisioned: you’re joining it, not creating it.

Profiles are the only correct way to switch environments

A profile bundles endpoint + auth + selected org under one name, and it’s the only thing that actually moves you between environments: each environment has its own auth session.

edisyl profile create local --use    # create + activate a profile on http://localhost:6001
edisyl login --profile local         # authenticate THAT profile

Order matters: a bare edisyl login authenticates default, not local.

Three ways to select a profile, highest priority first:

Selector	Use when
`--profile <name>` / `-p <name>`	One-off override on a single command
`EDISYL_PROFILE=<name>`	Persistent for a shell session or in CI
`edisyl profile use <name>`	Change the default for all future commands

Non-interactive / CI

Set EDISYL_API_KEY (and optionally EDISYL_API_URL). No profile needed. Mint keys with:

edisyl api-keys create

Tip: capture ids from any command with -j | jq -r '.id'. Every command supports -j/--json.

Next: Connect a data source.

Was this page helpful?

Thanks for the feedback.