inoyu -unomi

This MCP server provides a set of Apache Unomi profile and scope management tools that Claude can use to maintain user context across conversations. It exposes functions such as get_my_profile for retrieving or creating a profile based on environment or email, update_my_profile for modifying profile properties, and a suite of profile and consent-related operations (get_profile, search_profiles, create_scope, get_tenant_info, update_consent, get_consent, list_consents). The server also handles scope management automatically, including a default scope claude-desktop and automatic scope creation when needed. To use these tools, ensure Claude Desktop is configured with the unomi-server MCP entry, restart Claude Desktop after updating the config, and select the Unomi tools from the tools panel in the chat interface to perform profile lookups, updates, and consent actions. The tools communicate in JSON and support optional parameters for including segments, scores, and scope-related data as described in the available tool definitions (get_my_profile, update_my_profile, get_profile, search_profiles, create_scope, get_tenant_info, update_consent, get_consent, list_consents).

Prerequisites:

• Node.js and npm (or npx available)
• Access to an Apache Unomi server (V2 or V3) and proper credentials

Installation steps:

1. Install Claude Desktop and ensure MCP integration is enabled in your environment.
2. Add the MCP server configuration to Claude's config file (example shown below).
3. Replace environment variable placeholders with your actual Unomi server details.
4. Restart Claude Desktop to load the new MCP server configuration.

Example configuration (place in Claude config file, typically json):

{
  "mcpServers": {
    "unomi-server": {
      "command": "npx",
      "args": ["@inoyu/mcp-unomi-server"],
      "env": {
        "UNOMI_BASE_URL": "http://your-unomi-server:8181",
        "UNOMI_VERSION": "3",
        "UNOMI_USERNAME": "your-username",
        "UNOMI_PASSWORD": "your-password",
        "UNOMI_PROFILE_ID": "your-profile-id",
        "UNOMI_KEY": "your-unomi-key",
        "UNOMI_EMAIL": "your-email@example.com",
        "UNOMI_SOURCE_ID": "claude-desktop",
        "UNOMI_TENANT_ID": "your-tenant-id",
        "UNOMI_PUBLIC_KEY": "your-public-key",
        "UNOMI_PRIVATE_KEY": "your-private-key"
      }
    }
  }
}

Notes:

• The command uses npx to fetch and run the MCP Unomi server package on demand.
• Ensure environment variables match your Unomi deployment and authentication method (V2 or V3).

Tips and notes:

• The MCP server supports both Unomi V2 and V3 with automatic version detection; set UNOMI_VERSION accordingly.
• For V3, provide UNOMI_TENANT_ID, UNOMI_PUBLIC_KEY, and UNOMI_PRIVATE_KEY. For V2, provide UNOMI_USERNAME, UNOMI_PASSWORD, and UNOMI_KEY.
• The default scope used is claude-desktop; create_scope can be used to add additional scopes as needed.
• After updating the configuration, restart Claude Desktop to ensure the MCP tools are loaded.
• If you encounter connectivity issues, verify UNOMI_BASE_URL and network access from the host running Claude Desktop.
• All data exchanges are JSON formatted as described by each tool’s API surface.