Configuration & Execution | Alephant API Documentation

Based on the environment variables provided, the Alephant MCP server operates in two distinct permission modes. Understanding these modes is crucial for setting up the correct access level for your team or personal use.

Two Execution Modes

Mode	Environment Variables	Permissions	Tool Count
Virtual Key (VK)	`ALEPHANT_VIRTUAL_KEY`	Read-only, strictly scoped to a single cockpit	7
Manager	`ALEPHANT_PAT` + `ALEPHANT_WORKSPACE_ID`	Full workspace management and write access	15

Note: The Manager mode (PAT) takes precedence. If both are set, the server will operate in Manager mode. If neither is set, the process will exit with an error.

1. Virtual Key (VK) Mode - Read-Only

This mode is ideal for individual developers or agents who only need to monitor their own spending and budget. By providing a single ALEPHANT_VIRTUAL_KEY, the MCP server is restricted to querying data specifically associated with that key. It cannot create new keys, modify workspace settings, or view data from other departments.

2. Manager Mode - Full Access

Designed for FinOps administrators, Workspace Owners, and Team Leads. By providing a Personal Access Token (ALEPHANT_PAT) and a Workspace ID (ALEPHANT_WORKSPACE_ID), the MCP server gains full read/write access to the workspace. It can create new Virtual Keys, set department budgets, view cross-organization analytics, and enforce policies.

Transport Options

The Alephant MCP Server supports two standard transport layers:

Stdio (Local): Runs on your local machine and communicates via stdin/stdout. Ideal for local development, personal setups, and CLI tools. You can install it easily via npm/npx (npx -y @alephantai/mcp).
Streamable HTTP (Remote): Runs on a server with bidirectional communication via SSE/HTTP. Designed for team deployment, production environments, and hosted services (e.g., mcp.alephant.ai/mcp).