A Model Context Protocol server to access Apache Unomi data
Most developer tooling work still happens through a UI a human drives. Inoyu MCP Unomi Server MCP server moves it into the conversation instead. A Model Context Protocol server to access Apache Unomi data.
A Model Context Protocol server enabling Claude to maintain user context through Apache Unomi profile management.
This MCP server enables Claude to maintain context about users through Apache Unomi's profile management system. Here's what you can achieve with it:
Installation goes through your MCP client rather than a global install: point it at ensures on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The server publishes 14 tools. What each one is for:
get_my_profile — Get your profile using environment variablesrequireSegments — Include segment informationrequireScores — Include scoring informationupdate_my_profile — Update properties of your profileExample — jsonget_profile — Retrieve a specific profile by IDsearch_profiles — Search for profilescreate_scope — Create a new Unomi scopeget_tenant_info — Get information about the current tenant (V3 only)update_consent — Update a user's consent status using the modifyConsent eventconsentId — Unique identifier for the consentstatus — Consent status (GRANTED, DENIED, or REVOKED)Configuration is passed through the environment: UNOMI_BASE_URL, UNOMI_VERSION, UNOMI_USERNAME, UNOMI_PASSWORD, UNOMI_PROFILE_ID, UNOMI_KEY, UNOMI_EMAIL, UNOMI_SOURCE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Inoyu MCP Unomi Server's toolset — get_my_profile, requireSegments, requireScores and 11 more — is a fair guide to whether it matches your workflow. It is maintained by sergehuber; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Inoyu MCP Unomi Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_my_profile | Get your profile using environment variables |
| requireSegments | Include segment information |
| requireScores | Include scoring information |
| update_my_profile | Update properties of your profile |
| Example | json |
| get_profile | Retrieve a specific profile by ID |
| search_profiles | Search for profiles |
| create_scope | Create a new Unomi scope |
| get_tenant_info | Get information about the current tenant (V3 only) |
| update_consent | Update a user's consent status using the modifyConsent event |
| consentId | Unique identifier for the consent |
| status | Consent status (GRANTED, DENIED, or REVOKED) |
| typeIdentifier | Type identifier of the consent |
| scope | Scope for the consent (defaults to claude-desktop) |
{
"mcpServers": {
"unomi-server": {
"command": "npx",
"args": ["@inoyu/mcp-unomi-server"],
"env": {
"UNOMI_BASE_URL": "http://your-unomi-server:8181",
"UNOMI_VERSION": "3", // Use "2" for Unomi V2, "3" for Unomi V3 (default)
"UNOMI_USERNAME": "your-username", // Required for V2, fallback for V3
"UNOMI_PASSWORD": "your-password", // Required for V2, fallback for V3
"UNOMI_PROFILE_ID": "your-profile-id",
"UNOMI_KEY": "your-unomi-key", // Required for V2 only
"UNOMI_EMAIL": "your-email@example.com",
"UNOMI_SOURCE_ID": "claude-desktop",
"UNOMI_TENANT_ID": "your-tenant-id", // Required for V3
"UNOMI_PUBLIC_KEY": "your-public-key", // Required for V3
"UNOMI_PRIVATE_KEY": "your-private-key" // Required for V3
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UNOMI_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| UNOMI_VERSION | Configuration value read at startup. | Optional |
| UNOMI_USERNAME | Configuration value read at startup. | Optional |
| UNOMI_PASSWORD | Configuration value read at startup. | Optional |
| UNOMI_PROFILE_ID | Configuration value read at startup. | Optional |
| UNOMI_KEY | Credential the server authenticates with. | Yes |
| UNOMI_EMAIL | Configuration value read at startup. | Optional |
| UNOMI_SOURCE_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.