docs / reference/env-vars
Environment variables
Every environment variable used across the proxy, CLI, MCP server, and cloud control plane.
⏱ 6 min read
Proxy
| VARIABLE | SCOPE | DEFAULT |
|---|---|---|
| EKMIRE_API_KEY | required | — |
| EKMIRE_UPSTREAM | required | — |
| EKMIRE_CLOUD | optional | https://api.ekmire.com |
| EKMIRE_TARPIT_THRESHOLD_MS | optional | 800 |
| EKMIRE_TARPIT_CONSECUTIVE | optional | 3 |
| EKMIRE_SEMANTIC_BLOCK_SCORE | optional | 0.85 |
| EKMIRE_SEMANTIC_LOG_SCORE | optional | 0.60 |
| EKMIRE_SEMANTIC_FALLBACK | optional | pass |
| EKMIRE_LLM_TIMEOUT_MS | optional | 1500 |
| EKMIRE_SCRAPER_POISON | optional | true |
CLI
The CLI reads two environment variables. All other configuration is stored in ~/.ekmire/config (written by ekmire auth login).
| VARIABLE | SCOPE | DEFAULT | DESCRIPTION |
|---|---|---|---|
| EKMIRE_CLOUD | optional | https://api.ekmire.com | Override the control plane URL. Only needed for self-hosted deployments. |
NOTEThe API key is stored in
~/.ekmire/config after ekmire auth login, not in an environment variable. To use a different key without re-authenticating, write it directly to that file.MCP server
The MCP server (ekmire mcp start) inherits the same credentials and config from ~/.ekmire/config as the rest of the CLI. No additional environment variables are required.