What it does
The Alephant MCP server connects MCP hosts such as Cursor, Claude Desktop, Codex, OpenCode and Claude Code to Alephant BYO-key. It exposes FinOps metrics, usage summaries, daily and per-model cost data, and model listings. It runs in one of two modes. Virtual Key (VK) mode shows usage scoped to a single cockpit, with three VK-only tools and eight tools in total. Manager mode covers the whole workspace, with 27 tools in total, including budget status, virtual key management, agent, member and department analytics, subscription info, anomaly diagnosis and spend drill-downs. Two prompts are provided: cost_audit_report works in both modes, and cost_optimization is available in Manager mode only.
It suits teams that track AI spend across Alephant providers and models, or that need to limit what each credential can see. Each workspace or Personal Access Token needs its own server entry, so several workspaces are handled by defining several named entries with separate environment variables. A CLI audit command prints the cockpit scope and usage summary in VK mode, or the workspace ID and analytics overview in Manager mode.
Setup requires the ALEPHANT_API_BASE_URL variable. Either ALEPHANT_VIRTUAL_KEY or ALEPHANT_PAT with ALEPHANT_WORKSPACE_ID must be set, and if both are present the PAT takes precedence. ALEPHANT_RATE_LIMIT_RPM is optional, defaults to 60 requests per minute, and can be set to 0 to turn off client-side throttling. Client configuration examples are included for each supported host.
Limitations and requirements
Requires ALEPHANT_API_BASE_URL. Requires either ALEPHANT_VIRTUAL_KEY or ALEPHANT_PAT with ALEPHANT_WORKSPACE_ID; the process exits with an error if neither is set and does not return mock data. Manager mode requires a Personal Access Token and workspace ID. The get_request_logs tool is not included because it uses a JWT-only backend route. On Windows, running npx from the repository root can fail with a command-not-recognised error, so the publisher recommends other directories or the shim in published versions 0.0.2 and later.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.AlephantAI/alephant-mcp
Alephant MCP server for AI cost control, BYO-key routing, 50+ providers, and 320+ models.
v0.1.3As shown on registry.modelcontextprotocol.io when we last read it