Inoyu Apache Unomi MCP Server
@sergehuber
An implementation of Anthropic's Model Context Protocol for the Apache Unomi CDP
Overview
What is Inoyu Apache Unomi MCP Server?
A Model Context Protocol server that enables Claude to maintain user context through Apache Unomi profile management. It integrates with Apache Unomi (versions 2 and 3) for user recognition, context storage, and consent management. This is an early implementation intended for demonstration and learning, not for production use.
How to use Inoyu Apache Unomi MCP Server?
Install via npx @inoyu/mcp-unomi-server and configure environment variables (UNOMI_BASE_URL, UNOMI_VERSION, authentication keys) in the Claude Desktop configuration file. Restart Claude Desktop after configuration.
Key features of Inoyu Apache Unomi MCP Server
- Email-based profile lookup with automatic creation
- Profile properties, segments, and scores access
- Automatic session management with date-based IDs
- Consent management with GDPR-compliant expiration
- Scope management with automatic scope creation
- Supports both Apache Unomi V2 and V3
Use cases of Inoyu Apache Unomi MCP Server
- Maintain user preferences across conversations with Claude
- Store and retrieve user-specific information persistently
- Manage user consent preferences and comply with privacy regulations
- Identify users across sessions using email or profile ID
FAQ from Inoyu Apache Unomi MCP Server
What are the runtime dependencies?
A running Apache Unomi server, Claude Desktop, network access to the Unomi server, and proper environment variables.
Where does user profile data live?
All profile data is stored in the Apache Unomi server; the MCP server acts as a bridge and does not persist data itself.
What are the known limitations of this implementation?
This early implementation only supports profile lookup/creation, property management, basic session handling, and scope management. Events, segments, session properties, and other Unomi features are not yet implemented.
How does authentication work for Unomi V2 versus V3?
V2 uses system administrator credentials (username, password, and key). V3 uses tenant-based authentication with a tenant ID, public key, and private key for different endpoint types.
