> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eigenai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# /configure

> Update EigenData-CLI settings including API key, MCP server URL, and schema file.

The `/configure` command manages EigenData-CLI settings. You can update your API key, MCP server URL, and schema file path. For initial setup, see [Getting Started](/products/eigendata-cli/getting-started).

## Settings

Settings are organized into two groups:

**Global settings** are stored in `~/.eigendata/settings.yaml` and apply across all projects.

| Setting   | Description                          | Required | Clearable |
| --------- | ------------------------------------ | -------- | --------- |
| `api_key` | EigenData API key for authentication | Yes      | No        |

**Project settings** are stored in `./eigendataDB/config/user_config.yaml` and apply to the current project.

| Setting          | Description                                                                          | Required | Clearable |
| ---------------- | ------------------------------------------------------------------------------------ | -------- | --------- |
| `mcp_server_url` | [MCP server](/products/eigendata-cli/core-concepts/mcp-server) URL for schema source | No       | Yes       |
| `schema_file`    | Path to local schema file (JSON/YAML)                                                | No       | Yes       |

<Note>`mcp_server_url` and `schema_file` can be cleared by entering `-` as the value.</Note>

<Tip>
  Other settings like [reference document](/products/eigendata-cli/core-concepts/domain) and sample count are configured per task during command execution, not through `/configure`. See [Domain & Reference Document](/products/eigendata-cli/core-concepts/domain) for details.
</Tip>

## Interactive configuration

### Step 1 — Open the settings menu

Run the configure command without arguments to see all available settings:

```
eigendata> /configure
```

The CLI displays two tables — global and project settings — followed by a numbered menu:

```
Global Settings (stored in ~/.eigendata/)
# Key          Value
1 api_key      sk-xxxx…xxxx

Project Settings (stored in ./eigendataDB/)
# Key             Value
2 mcp_server_url  http://localhost:8000
3 schema_file     ./my_functions.json

Select a setting to update (or 'q' to cancel):
```

### Step 2 — Select and update a setting

Enter the number of the setting you want to change:

```
Select a setting to update (or 'q' to cancel): 2

MCP Server URL
Example: http://127.0.0.1:8000
Type '-' to clear

> http://192.168.1.100:8000
```

The CLI confirms the update:

```
✓ Updated mcp_server_url
```

## Direct configuration

You can also configure settings directly without the interactive menu.

### View current value

Pass the setting name to see its current value:

```
eigendata> /configure api_key

api_key: sk-****...****
```

### Set a new value

Pass both the setting name and new value:

```
eigendata> /configure mcp_server_url http://localhost:9000

✓ mcp_server_url updated to: http://localhost:9000
```

### Clear an optional setting

Use `-` to clear optional settings:

```
eigendata> /configure mcp_server_url -

✓ Updated mcp_server_url
```

## Environment Variables

You can set API key via environment variable:

| Environment Variable | Setting   |
| -------------------- | --------- |
| `EIGENDATA_API_KEY`  | `api_key` |

Environment variables are read at startup. Settings configured via `/configure` take precedence.