The server has been designed to support external tracing and monitoring solutions. The MCP logging implementation has been intentionally removed in favor of a more robust tracing approach that will be implemented separately.
Note: Do not attempt to re-implement the previous logging system. A new tracing solution will be provided in the future.
Configuration fields explained:
`command`: Full path to the Python executable in your virtual environment
`args`: Array containing the full path to the MCP server script
`env`: Environment variables for configuration
- `MONGODB_URI`: MongoDB connection string
- `SQLITE_DB_PATH`: Absolute path to SQLite database file
- `EMBEDDING_BASE_URL`: Ollama server URL
- `EMBEDDING_MODEL`: Model to use for embeddings
- `LLM_MODEL`: Model to use for LLM operations
- `COLLECTION_NAME`: Name of the MongoDB collection to use (required)
- `PROCESS_DELETED_ITEMS`: Whether to process emails from the Deleted Items folder (optional, default: "false")
`disabled`: Whether the server is disabled (should be false)
`alwaysAllow`: Array of tools that don't require user confirmation
`autoApprove`: Array of tools that can be auto-approved
Replace the paths with the actual paths on your system. Note that Windows paths in the `env` section should use double backslashes.
Available Tools
1. process_emails
Process emails from a specified date range:
The tool will:
Connect to specified Outlook mailboxes
Retrieve emails from Inbox and Sent Items folders (and Deleted Items if enabled)
Store emails in SQLite database
Generate embeddings using Ollama
Store embeddings in MongoDB for semantic search
Example Usage in Claude
Architecture
The server uses a hybrid search approach:
SQLite database for:
- Primary email storage
- Full-text search capabilities
- Processing status tracking
- Efficient filtering
- Directory is created automatically if it doesn't exist
- Connections are properly closed to prevent database locking
MongoDB for:
- Vector embeddings storage
- Semantic similarity search
- Metadata filtering
- Efficient retrieval
- Connections are properly closed after use
Error Handling
The server provides detailed error messages for common issues:
Invalid date formats
Connection issues with Outlook
MongoDB errors
Embedding generation failures with retry logic
SQLite storage errors
Ollama server connection issues with automatic retries
Resource Management
The server implements proper resource management to prevent issues:
Database connections (SQLite and MongoDB) are kept open during the server's lifetime to prevent "Cannot operate on a closed database" errors
Connections are only closed when the server shuts down, using an atexit handler
Destructors and context managers are used as a fallback to ensure connections are closed when objects are garbage collected
Connection management is designed to balance resource usage with operational reliability
Robust retry logic for external services like Ollama to handle temporary connection issues
Security Notes
The server only processes emails from specified mailboxes
All data is stored locally (SQLite) and in MongoDB
No external API calls except to local Ollama server
Requires explicit user approval for email processing
No sensitive email data is exposed through the MCP interface
Debugging
If you encounter issues:
Verify emails were successfully processed (check process_emails response)
Ensure Ollama server is running for embedding generation