Unomi already holds the customer profile; this lets a conversation read and write that same record, so what the assistant learns is stored where the rest of the business can already see it.
An MCP server that connects a client to an Apache Unomi profile store. It looks a profile up by email and creates one when there is none, reads and writes properties on your own profile, searches profiles, and creates scopes that keep one context's data apart from another's.
- Your own profile read back, optionally with its segments and scores
- Properties written onto your own profile
- Another profile fetched by id
- Profiles searched across the store
- A scope created, so one context's data stays separate from another's
A running Apache Unomi server, and a fair amount of configuration: the Unomi base URL and which major version it is, plus the credentials that version needs - username, password and an API key for V2, or a tenant id and a key pair for V3 - along with the profile id, contact email and source id it should use. The author marks it an early implementation not validated for production, and says events, segments and session properties are not implemented yet.
One command plus a key — npx @inoyu/mcp-unomi-server, then supply credentials