Log inSubmit server
Inoyu MCP Unomi Server logo

Inoyu MCP Unomi Server

by sergehuber

Connects MCP clients to Apache Unomi for profile lookup, updates, searches, scopes, tenant data, and consent management.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Inoyu MCP Unomi Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sergehuber-inoyu-mcp-unomi-server": {
      "command": "npx",
      "args": [
        "@inoyu/mcp-unomi-server"
      ],
      "env": {
        "UNOMI_BASE_URL": "YOUR_VALUE_HERE",
        "UNOMI_VERSION": "YOUR_VALUE_HERE",
        "UNOMI_PROFILE_ID": "YOUR_VALUE_HERE",
        "UNOMI_EMAIL": "YOUR_VALUE_HERE",
        "UNOMI_USERNAME": "YOUR_VALUE_HERE",
        "UNOMI_PASSWORD": "YOUR_VALUE_HERE",
        "UNOMI_TENANT_ID": "YOUR_VALUE_HERE",
        "UNOMI_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

sergehuber/inoyu-mcp-unomi-server MCP server connects an MCP client to Apache Unomi profile and tenant APIs. It supports Unomi V2 and V3 authentication, profile lookup by ID or email, property updates, profile searches, scope creation, and consent operations. Use it when an agent needs to read or maintain user context stored in an Apache Unomi CDP. The implementation is intended for demonstration, learning, and experimentation rather than production use.

Use cases

  • Retrieve a user's Unomi profile during an agent conversation
  • Update profile preferences and properties
  • Search Unomi profiles by name or email
  • Create scopes for separate applications or contexts
  • Inspect and update user consent records

Key features

  • Apache Unomi V2 and V3 support
  • Profile lookup by ID or email
  • Profile property updates
  • Profile search with pagination
  • Scope creation and automatic default scope handling
  • Consent and tenant information operations

Tools6

What Inoyu MCP Unomi Server lets your agent do. Expand a tool for its parameters.

Self-reported~72 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

18/19 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @inoyu/mcp-unomi-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars11Stargazers on the source repository.
Last commit22d agoMost recent push to the default branch.
Tools exposed6Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How Inoyu MCP Unomi Server works

What sergehuber/inoyu-mcp-unomi-server MCP server does

sergehuber/inoyu-mcp-unomi-server MCP server exposes Apache Unomi profile-management operations through MCP. It can identify a profile from an environment-configured profile ID or email address, retrieve a profile directly by ID, search profiles by name or email fields, and update profile properties. Property values may be strings, numbers, booleans, or nulls.

The server also supports scope management. Agents can create scopes with an identifier, name, and description, while the implementation uses a default claude-desktop scope and can create missing scopes when needed. Unomi V3 deployments can expose tenant information, including version and key status.

Consent queries can use a profile from the environment or an explicitly supplied profile ID, with optional status and scope filters.

How it works

The package runs as an MCP process and communicates with Apache Unomi using the configured base URL and authentication settings. Install and launch it through npx @inoyu/mcp-unomi-server, then register the process in an MCP client configuration.

UNOMI_VERSION=2 selects the legacy authentication flow, which uses a username, password, and key. Version 3 is the default and uses tenant-based credentials: a tenant ID, public key, and private key. Public and private Unomi endpoints use different authentication methods under V3. Profile operations use tenant authentication, while public context requests use the public API key.

For profile-oriented operations, the server can use UNOMI_PROFILE_ID directly or resolve a profile from UNOMI_EMAIL. The implementation generates a date-based session ID for the profile tools. Profile data and other exchanges use JSON.

Setup and configuration

Add the server to the Claude Desktop configuration file at the platform-specific location documented by the project, then restart Claude Desktop. Set UNOMI_BASE_URL to the Apache Unomi address and select the matching version. V2 requires UNOMI_USERNAME, UNOMI_PASSWORD, and UNOMI_KEY; V3 requires UNOMI_TENANT_ID, UNOMI_PUBLIC_KEY, and UNOMI_PRIVATE_KEY.

UNOMI_SOURCE_ID identifies the source used by the client configuration. UNOMI_PROFILE_ID and UNOMI_EMAIL determine the default profile context. A custom scope can be supplied to consent operations, while the default scope is claude-desktop when no scope is specified.

Tools and capabilities

sergehuber/inoyu-mcp-unomi-server MCP server provides these documented operations:

  • get_my_profile: retrieves the configured or email-resolved profile, with optional segment and score data.
  • update_my_profile: changes properties on the configured or email-resolved profile.
  • get_profile: retrieves complete profile data by profile ID.
  • search_profiles: searches first name, last name, and email fields with limit and offset options.
  • create_scope: creates a scope with optional descriptive metadata.
  • get_tenant_info: returns tenant details for Unomi V3.
  • update_consent, get_consent, and list_consents: manage and inspect consent records, including status, scope, and metadata.

Scopes are required for some profile and event-related operations. The server can create the default scope automatically, or an agent can create a named scope explicitly.

Limitations and notes

sergehuber/inoyu-mcp-unomi-server MCP server is described as an early implementation. Unomi features such as events, segments, and session properties are not generally implemented, although profile retrieval can request segment and score information.

Authentication configuration differs substantially between Unomi V2 and V3, so credentials must match the selected version. Consent expiration behavior documented by the project sets granted consent to expire after one year and denied or revoked consent to expire immediately.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Inoyu MCP Unomi Server

sergehuber/inoyu-mcp-unomi-server is an MCP server that connects AI clients to Apache Unomi profile and tenant APIs. Its main tools retrieve, search, and update profiles, create scopes, inspect tenant information in Unomi V3, and manage user consent records. It supports both Unomi V2 and V3 authentication configurations.

Install it by configuring an MCP client to run `npx @inoyu/mcp-unomi-server`. For Claude Desktop, add the command and its environment variables to the platform-specific `claude_desktop_config.json`, then restart the application.

Set `UNOMI_VERSION=3`, `UNOMI_TENANT_ID`, `UNOMI_PUBLIC_KEY`, and `UNOMI_PRIVATE_KEY`, along with `UNOMI_BASE_URL`. V3 is the default mode and uses tenant-based authentication for private operations and the public key for public context requests.

Yes, it supports Apache Unomi V2. Set `UNOMI_VERSION=2` and provide `UNOMI_USERNAME`, `UNOMI_PASSWORD`, and `UNOMI_KEY` for the legacy authentication flow.

Yes, the documented consent tools can update, retrieve, and list consent records. They support granted, denied, and revoked statuses, with optional consent type, scope, metadata, profile ID, and status filters.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewInoyu MCP Unomi Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sergehuber-inoyu-mcp-unomi-server?style=directory)](https://allmcps.com/mcp/sergehuber-inoyu-mcp-unomi-server)
HTML Embed
<a href="https://allmcps.com/mcp/sergehuber-inoyu-mcp-unomi-server"><img src="https://allmcps.com/api/badge/sergehuber-inoyu-mcp-unomi-server?style=directory" alt="Inoyu MCP Unomi Server on AllMCPs" /></a>