Inoyu Apache Unomi MCP Server
by MCP-Mirror
This is a Model Context Protocol (MCP) server that enables Claude to maintain user context through Apache Unomi profile management. It's an early implementation intended for demonstration purposes, not validated for production use.
Last updated: N/A
What is Inoyu Apache Unomi MCP Server?
This MCP server enables Claude to maintain context about users through Apache Unomi's profile management system. It provides profile lookup and creation using email, profile property management, basic session handling, and scope management for context isolation.
How to use Inoyu Apache Unomi MCP Server?
To use with Claude Desktop, add the server config and environment variables to the claude_desktop_config.json file. Ensure the UNOMI_BASE_URL, UNOMI_USERNAME, UNOMI_PASSWORD, UNOMI_PROFILE_ID, UNOMI_KEY, UNOMI_EMAIL, and UNOMI_SOURCE_ID environment variables are correctly configured. Restart Claude Desktop after updating the configuration.
Key features of Inoyu Apache Unomi MCP Server
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
Use cases of Inoyu Apache Unomi MCP Server
Have Claude remember user preferences across conversations
Store and retrieve user-specific information
Maintain consistent user context
Manage multiple users through email identification
FAQ from Inoyu Apache Unomi MCP Server
What if protected events are failing?
What if protected events are failing?
Verify Unomi key matches exactly in both configurations, check IP address is correctly whitelisted, ensure scope exists before updating properties, and verify CORS configuration if needed.
What if a profile is not found?
What if a profile is not found?
Check if UNOMI_EMAIL is correctly set, verify email format is valid, ensure profile exists in Unomi, and check if fallback UNOMI_PROFILE_ID is valid.
What if there are session issues?
What if there are session issues?
Remember sessions are date-based, only one session per profile per day, check session ID format matches profileId-YYYYMMDD, and verify scope exists for session.
What if there are connection problems?
What if there are connection problems?
Verify Unomi server is running, check network connectivity, ensure UNOMI_BASE_URL is correct, and verify authentication credentials.
How do I debug the server?
How do I debug the server?
Use the MCP Inspector by running npm run inspector or tail the Claude Desktop logs to see MCP requests and responses.