Revenium MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging verbosity level | |
| TOOL_PROFILE | No | Choose profile: 'starter' (7 tools) or 'business' (18 tools) | |
| REQUEST_TIMEOUT | No | API request timeout in seconds | |
| REVENIUM_API_KEY | Yes | Your Revenium API key | |
| REVENIUM_TEAM_ID | No | Multi-tenant environments | |
| REVENIUM_BASE_URL | No | API endpoint URL (defaults to main Revenium instance) | |
| REVENIUM_OWNER_ID | No | Non-primary user scenarios | |
| REVENIUM_TENANT_ID | No | Operating on behalf of different tenant | |
| REVENIUM_APP_BASE_URL | No | Revenium application/analytics host | |
| REVENIUM_DEFAULT_EMAIL | No | Custom alert email preferences |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| system_setupC | Unified system setup and onboarding combining welcome guidance, setup checklist, and email verification. Key actions: show_welcome, setup_checklist, check_status, validate_email. Use get_capabilities() for complete action list. |
| slack_managementC | Unified Slack integration management combining configuration, OAuth workflow, and setup assistance. Key actions: list_configurations, get_configuration, set_default_configuration, initiate_oauth, guided_setup, quick_setup. Use get_capabilities() for complete action list. |
| tool_introspectionD | Tool introspection providing detailed description of each tool's function |
| manage_alertsB | AI spending alerts and anomaly monitoring with three alert types: (1) Spike Detection - create_threshold_alert for real-time monitoring, (2) Budget Threshold - create_cumulative_usage_alert for period tracking, (3) Relative Change - create with alertType RELATIVE_CHANGE and INCREASES_BY/DECREASES_BY operators for trend detection. Supports persistence-based triggering with triggerAfterPersistsDuration. Use get_examples() for comprehensive usage guidance. |
| business_analytics_managementC | Business analytics and cost analysis with enhanced statistical anomaly detection and new entity detection. Key actions: get_provider_costs, get_model_costs, get_customer_costs, get_api_key_costs, get_agent_costs, get_user_costs, get_tool_costs, get_top_tools, get_tool_costs_by_agent, get_tool_costs_by_provider, get_cost_summary, analyze_cost_anomalies. For anomaly detection use: min_impact_threshold, include_dimensions. For new entity detection use: detect_new_entities, min_new_entity_threshold. Use get_examples() for parameter guidance and get_capabilities() for status. |
| manage_meteringC | Submit AI transaction metering metadata and lookup existing AI transactions metered by Revenium. Receive guidance for writing new integrations to Revenium's AI metering API using python and typescript. Key actions: submit_ai_transaction, lookup_transactions (requires transaction IDs), lookup_recent_transactions (browse without IDs), get_integration_guide, list_ai_models, validate. Supports Python and JavaScript integration examples. Use get_capabilities() for full guidance. |
| system_diagnosticsC | Unified system diagnostics combining configuration analysis, auto-discovery debugging, and log analysis. Key actions: environment_variables, debug, get_internal_logs, analyze_operations. Use get_capabilities() for complete action list. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct area: cost analytics, alerts, metering, Slack integration, diagnostics, setup, and introspection. There is no functional overlap despite some shared themes like anomaly detection in both analytics and alerts.
Tool names use snake_case but mix patterns: some start with 'manage_' (verb_noun) while others are noun_noun (e.g., 'slack_management', 'system_diagnostics'). This inconsistency could confuse an agent about naming conventions.
With 7 tools, the server covers the essential domains (costs, alerts, metering, Slack, system, introspection) without bloat. Each tool earns its place, and the count is well-scoped for the stated purpose.
The tool surface is comprehensive for AI spending management, including cost analytics, alerting, metering submission/system, Slack integration, and system upkeep. Minor gaps (e.g., user/role management) exist but do not hinder core workflows.