Alephant MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALEPHANT_PAT | No | Personal Access Token for manager mode | |
| ALEPHANT_VIRTUAL_KEY | No | Virtual key for read-only scoped mode | |
| ALEPHANT_API_BASE_URL | Yes | Base URL for the Alephant API (required for both modes) | |
| ALEPHANT_WORKSPACE_ID | No | Workspace ID (required when using PAT) | |
| ALEPHANT_RATE_LIMIT_RPM | No | Rate limit in requests per minute (default 60, use 0 to disable client-side throttling) | 60 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_alephant_connectionA | Checks Alephant API connectivity and credential usability for the current MCP mode. |
| get_usage_summaryA | Returns total spend, requests, and token usage for the selected period. |
| get_daily_costsA | Returns daily AI spend for the selected period. |
| get_cost_by_modelA | Breaks down AI spend and request volume by model for the selected period. |
| list_available_modelsA | Lists models available through Alephant for the current credential scope. |
| get_my_scopeA | Returns the current virtual key scope, limits, and accessible resources. |
| get_my_budgetA | Returns budget status for the current virtual key. |
| get_my_recent_requestsB | Returns recent requests made with the current virtual key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| cost_audit_report |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct aspect: connection check, cost breakdowns (by model, daily, total), budget status, recent requests, scope, and model listing. No two tools have overlapping purposes.
All tools follow a consistent verb_noun pattern (e.g., check_alephant_connection, get_cost_by_model, list_available_models) with clear, predictable naming.
With 8 tools, the server is well-scoped for monitoring and managing Alephant API usage. The count is neither too sparse nor excessive.
The set covers essential monitoring needs (connection, costs, budget, requests, scope, models). Missing are management actions like updating budgets or keys, but the core monitoring surface is complete.