# Connect to your server

The tool talks to exactly one server and needs its address and an access token. You
create the token in Lalabase under **API Tokens** in the account menu.

## Take it from Claude Code

If Claude Code already has your Lalabase server, take it from there. The command lists
what it finds, asks which entry to use and checks the token before saving:

```sh
lalabase auth import
```

## Enter it by hand

Otherwise create `~/.config/lalabase/config.toml`:

```toml
[profiles.default]
url = "https://lalabase.example.com"
token = "your-token"
```

The file must be readable by you alone, or the tool refuses it:

```sh
chmod 700 ~/.config/lalabase
chmod 600 ~/.config/lalabase/config.toml
```

## Run it

```sh
lalabase auth status    # who the token belongs to, what the server supports
lalabase                # open the interface
```

What you see depends on your server and your token: a key appears only when the server
supports it and the token may use it. With a read-only token you can read everything,
but `r`, `b` and `k` are gone.