
Alephant Mcp
Monitor and control LLM spend from your agent cockpit while routing calls through Alephant with BYO keys across many providers and models.
Overview
Alephant MCP is an Operate-phase MCP server for the infra subphase that exposes Alephant cost control, BYO-key routing, and multi-provider model governance to agents via stdio npm.
What is this MCP server?
- Documented scale: 50+ providers and 320+ models in server description
- BYO-key routing with Virtual Key (read-only cockpit) or Personal Access Token Manager mode
- stdio npm package @alephantai/mcp (version 0.1.3)
- Configurable ALEPHANT_RATE_LIMIT_RPM and workspace-scoped manager access
- 50+ providers and 320+ models cited in registry description
- Registry version 0.1.3
- npm identifier: @alephantai/mcp
What problem does it solve?
Agent-driven coding silently multiplies LLM bills across providers with no single cockpit for keys, limits, or usage in your workspace.
Who is it for?
Indie SaaS builders shipping agent features who already use Alephant and want MCP-native spend visibility and key management from the IDE.
Skip if: Hobby projects with a single static API key and no need for workspace billing, or teams not on the Alephant platform.
What do I get? / Deliverables
After configuring Alephant base URL and Virtual Key or PAT workspace credentials, your agent can query and manage cost-aware routing from the Alephant plane.
- MCP-connected Alephant cockpit for usage and routing queries from your agent
- Configured VK or Manager authentication with optional ALEPHANT_RATE_LIMIT_RPM
- Operational visibility across Alephant’s documented 50+ providers and 320+ models surface
Recommended MCP Servers
Journey fit
Cost governance and provider routing matter most once you ship and run AI features in production, not during first prototype prompts. Infra is the shelf for operational control planes—virtual keys, workspaces, and rate limits that keep agent spend predictable.
How it compares
AI spend and routing control plane MCP, not a model host or prompt library skill.
Common Questions / FAQ
Who is Alephant MCP for?
It is for developers and managers on Alephant who want MCP tools for cost control, virtual keys, and multi-provider routing from Claude Code or similar clients.
When should I use Alephant MCP?
Use it when production or heavy dev agent usage needs workspace-scoped usage visibility, BYO-key policies, rate limits, or manager-mode controls.
How do I add Alephant MCP to my agent?
Add @alephantai/mcp as a stdio MCP server, set ALEPHANT_API_BASE_URL, then supply ALEPHANT_VIRTUAL_KEY for VK mode or ALEPHANT_PAT with ALEPHANT_WORKSPACE_ID for Manager mode (PAT wins if both are set).