Inoyu Apache Unomi MCP Server
by sergehuber
The Inoyu Apache Unomi MCP Server 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 acts as a bridge between Claude and Apache Unomi, allowing Claude to access and manage user profiles, properties, and sessions within Unomi. It provides tools for profile lookup, creation, and updating, enabling Claude to maintain consistent user context across conversations.
How to use Inoyu Apache Unomi MCP Server?
To use this server, you need to configure it within Claude Desktop by adding the server configuration and environment variables to the claude_desktop_config.json file. Ensure that the environment variables point to a running Apache Unomi instance with the correct credentials and key. Restart Claude Desktop after updating the configuration.
Key features of Inoyu Apache Unomi MCP Server
Email-based profile lookup and creation
Profile property management
Basic session handling
Scope management for context isolation
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 between sessions
Manage multiple users through email identification
FAQ from Inoyu Apache Unomi MCP Server
What is the purpose of the Unomi key?
What is the purpose of the Unomi key?
The Unomi key is used for authorization of protected events like property updates. It must match exactly between the server configuration and the UNOMI_KEY environment variable.
How does the server resolve the profile ID?
How does the server resolve the profile ID?
The server first attempts to find a profile using the email provided in the UNOMI_EMAIL environment variable. If that fails or the variable is not set, it falls back to using the UNOMI_PROFILE_ID.
What is a scope in Unomi?
What is a scope in Unomi?
A scope is a namespace used to isolate events and profile updates. The server automatically manages a default scope but custom scopes can be created for different applications or contexts.
How are sessions managed?
How are sessions managed?
The server automatically generates session IDs based on the profile ID and current date in the format profileId-YYYYMMDD. Only one session per profile per day is supported.
What do I do if I encounter protected events failing?
What do I do if I encounter protected events failing?
Verify the Unomi key matches in both configurations, check the IP address is whitelisted in Unomi, ensure the scope exists before updating properties, and verify the CORS configuration if needed.