inoyu-mcp-unomi-server

WHAT IT CONNECTS

What inoyu-mcp-unomi-server gives an AI Agent

• Email-based profile lookup with automatic creation
• Profile properties, segments, and scores access
• JSON format for all data exchange
• Automatic session management with date-based IDs
• `get_my_profile` - Get your profile using environment variables
• Uses UNOMI_PROFILE_ID from environment or email lookup
• Automatically generates a session ID based on the current date
• Optional parameters:
• requireSegments: Include segment information
• requireScores: Include scoring information
• `update_my_profile` - Update properties of your profile
• Uses UNOMI_PROFILE_ID from environment or email lookup
• Takes a properties object with key-value pairs to update
• Supports string, number, boolean, and null values
• Example:
• `get_profile` - Retrieve a specific profile by ID
• Takes profileId as required parameter
• Returns full profile data from Unomi
• `search_profiles` - Search for profiles
• Takes query string and optional limit/offset parameters
• Searches across firstName, lastName, and email fields
• `create_scope` - Create a new Unomi scope
• Takes scope identifier and optional name/description
• Required for event tracking and profile updates
• Example:
• Default Scope:
• A default scope `claude-desktop` is used for all operations
• Created automatically when needed
• Used for profile updates and event tracking
• Custom Scopes:
• Can be created using the `create_scope` tool
• Useful for separating different applications or contexts
• Must exist before using in profile operations
• Automatic Scope Creation:
• The server checks if required scopes exist
• Creates them automatically if missing
• Uses meaningful defaults for scope metadata
• **User Recognition**:
• Identify users across conversations using email or profile ID
• Maintain consistent user context between sessions
• Automatically create and manage user profiles
• **Context Management**:
• Store and retrieve user preferences
• **Integration Features**:
• Seamless Claude Desktop integration
• Automatic session management
• Scope-based context isolation
• Have Claude remember user preferences across conversations
• Store and retrieve user-specific information
• Maintain consistent user context
• Manage multiple users through email identification
• Running Apache Unomi server
• Claude Desktop installation
• Network access to Unomi server
• Proper security configuration
• Required environment variables
• Email Lookup (if `UNOMI_EMAIL` is set):
• Searches for a profile with matching email
• If found, uses that profile's ID
• Useful for maintaining consistent profile across sessions
• Fallback Profile ID:
• If email lookup fails or `UNOMI_EMAIL` is not set
• Uses the `UNOMI_PROFILE_ID` from environment
• Ensures a profile is always available
• `"email_lookup"`: Profile found via email
• `"environment"`: Using fallback profile ID
• Configure protected events in `etc/org.apache.unomi.cluster.cfg`:
• Ensure your Unomi server has CORS properly configured in `etc/org.apache.unomi.cors.cfg`:
• Restart Unomi server to apply changes
• Email Lookup (if `UNOMI_EMAIL` is set):
• Searches for a profile with matching email
• If found, uses that profile's ID
• Useful for maintaining consistent profile across sessions
• Fallback Profile ID:
• If email lookup fails or `UNOMI_EMAIL` is not set
• Uses the `UNOMI_PROFILE_ID` from environment
• Ensures a profile is always available
• `"email_lookup"`: Profile found via email
• `"environment"`: Using fallback profile ID
• Configure protected events in `etc/org.apache.unomi.cluster.cfg`:
• Ensure your Unomi server has CORS properly configured in `etc/org.apache.unomi.cors.cfg`:
• Restart Unomi server to apply changes
• **Protected Events Failing**
• Verify Unomi key matches exactly in both configurations
• Check IP address is correctly whitelisted
• Ensure scope exists before updating properties
• Verify CORS configuration if needed
• **Profile Not Found**
• Check if UNOMI_EMAIL is correctly set
• Verify email format is valid
• Ensure profile exists in Unomi
• Check if fallback UNOMI_PROFILE_ID is valid
• **Session Issues**
• Remember sessions are date-based
• Only one session per profile per day
• Check session ID format matches `profileId-YYYYMMDD`
• Verify scope exists for session
• **Connection Problems**
• Verify Unomi server is running
• Check network connectivity
• Ensure UNOMI_BASE_URL is correct
• Verify authentication credentials
• **Claude Desktop Logs**:
• **Unomi Server Logs**:
• **Reset State**:
• **Verify Configuration**:
• Create or edit your Claude Desktop configuration:
• MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
• Windows: `%APPDATA%/Claude/claude_desktop_config.json`
• Add the server configuration using NPX: