OpenAI Token Manager MCP
Provides intelligent OpenAI API token management with automatic switching between model tiers when usage limits are reached. It enables users to track daily token consumption, estimate costs before making calls, and manage project-specific usage data.
README
OpenAI Token Manager MCP Server
A Model Context Protocol (MCP) server that provides intelligent OpenAI API token usage management with automatic model switching capabilities.
Features
- Automatic Model Switching: Automatically switches between model tiers (gpt-4o → gpt-4o-mini) when token limits are reached
- Daily Token Tracking: Tracks token usage per model with daily reset functionality
- Token Estimation: Estimate token usage before making API calls
- Progress Tracking: Resume processing from where you left off
- Configurable Limits: Customizable token limits and model tiers
- Comprehensive Logging: Detailed logging for debugging and monitoring
Installation
- Clone or download this repository
- Install the package:
pip install -e .
Quick Start
Using with Claude Desktop
Add this server to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"openai-token-manager": {
"command": "python",
"args": ["-m", "openai_token_manager_mcp.server"],
"env": {
"OPENAI_API_KEY": "your-openai-api-key-here"
}
}
}
}
Using Programmatically
# Run the MCP server
python -m openai_token_manager_mcp.server
Available Tools
initialize_token_manager
Initialize the token manager with a specific project directory.
Parameters:
project_dir(string): Path to store token usage data
get_token_status
Get current token usage status and model information.
Returns: JSON with current model, usage statistics, and available models.
estimate_tokens
Estimate token usage for given prompts before making API calls.
Parameters:
system_prompt(string): The system promptuser_prompt(string): The user promptmodel(string, optional): Model to estimate for
call_openai_with_management
Call OpenAI API with automatic token management and model switching.
Parameters:
system_prompt(string): The system promptuser_prompt(string): The user promptresponse_format(string, optional): "json" for JSON response formattimeout(integer, optional): Request timeout in seconds (default: 45)force_model(string, optional): Force specific model (bypasses automatic switching)dry_run(boolean, optional): Simulate without making actual API call
switch_model
Manually switch to the next available model tier.
reset_daily_usage
Reset daily token usage counters.
Configuration
Model Tiers
The default configuration includes:
MODEL_TIERS = [
{"name": "gpt-4o", "max_tokens": 250_000, "stop_at": 240_000},
{"name": "gpt-4o-mini", "max_tokens": 2_500_000, "stop_at": 2_450_000}
]
You can modify these in the server.py file to match your needs.
Environment Variables
OPENAI_API_KEY: Your OpenAI API key (required)
Example Usage
Basic Token Management
# Initialize for a specific project
await call_tool("initialize_token_manager", {"project_dir": "/path/to/project"})
# Check current status
status = await call_tool("get_token_status", {})
# Estimate tokens before calling
estimate = await call_tool("estimate_tokens", {
"system_prompt": "You are a helpful assistant.",
"user_prompt": "What is the weather like?"
})
# Make managed API call
response = await call_tool("call_openai_with_management", {
"system_prompt": "You are a helpful assistant.",
"user_prompt": "Explain quantum computing in simple terms.",
"response_format": "json"
})
Advanced Usage
# Force a specific model
response = await call_tool("call_openai_with_management", {
"system_prompt": "You are a helpful assistant.",
"user_prompt": "Write a short story.",
"force_model": "gpt-4o",
"timeout": 60
})
# Dry run to test without API calls
dry_response = await call_tool("call_openai_with_management", {
"system_prompt": "You are a helpful assistant.",
"user_prompt": "Analyze this data.",
"dry_run": True
})
# Manually switch models
await call_tool("switch_model", {})
# Reset usage for new day
await call_tool("reset_daily_usage", {})
File Structure
When initialized, the token manager creates the following structure:
project_directory/
├── project_state/
│ └── token_usage.json # Token usage tracking
├── project_logs/
│ └── token_manager.log # Detailed logs
└── project_output/ # For any output files
Error Handling
The server includes comprehensive error handling:
- Rate Limiting: Automatic retry with exponential backoff
- Model Exhaustion: Graceful handling when all model tiers are exhausted
- API Errors: Detailed logging and error messages
- File Operations: Safe file handling with proper error reporting
Roadmap & Future Updates
Planned Features
- Multi-Provider Support: Add support for Anthropic Claude, Google Gemini, and other LLM providers
- Cost Tracking: Track actual costs alongside token usage with real-time pricing
- Team Management: Multi-user token pools and usage quotas for organizations
- Advanced Analytics: Detailed usage reports, trends, and optimization suggestions
- Custom Model Tiers: User-configurable model hierarchies and switching rules
- Webhook Integration: Real-time notifications for usage thresholds and model switches
- Dashboard UI: Web interface for monitoring and managing token usage
Performance Improvements
- Caching Layer: Intelligent response caching to reduce redundant API calls
- Batch Processing: Optimized handling of multiple concurrent requests
- Smart Retries: Enhanced retry logic with exponential backoff and circuit breakers
Integration Enhancements
- Claude Desktop Plugin: Native integration for seamless usage tracking
- VS Code Extension: Direct IDE integration for development workflows
- Cursor Extension: Native support for Cursor IDE workflows and AI coding assistance
- API Gateway: REST API wrapper for non-MCP integrations
Want to see a specific feature? Open an issue to request it!
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Test thoroughly
- Submit a pull request
License
MIT License - see LICENSE file for details
Support
For issues and questions:
- Create an issue on GitHub
- Check the logs in
project_logs/token_manager.logfor detailed error information
Changelog
v1.0.0
- Initial release
- Basic token management and model switching
- MCP server implementation
- Comprehensive logging and error handling
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.