Inoyu

Created By
a year ago
Interact with an Apache Unomi CDP customer data platform to retrieve and update customer profiles
Overview

What is Inoyu?

Inoyu is an early-stage implementation of an Apache Unomi Model Context Protocol server, designed to maintain user context and manage customer profiles within a customer data platform (CDP).

How to use Inoyu?

To use Inoyu, install it on your machine and configure it to work with your Apache Unomi server. Set the necessary environment variables and add the server configuration to your Claude Desktop application.

Key features of Inoyu?

  • Email-based profile lookup and creation
  • Management of profile properties and basic session handling
  • Automatic context isolation through scope management

Use cases of Inoyu?

  1. Maintaining user profiles across different sessions in Claude Desktop.
  2. Automating customer data retrieval for personalized customer interactions.
  3. Managing user preferences and activities for targeted marketing.

FAQ from Inoyu?

  • Is Inoyu production-ready?

No, Inoyu is an early implementation intended for educational and experimental purposes only.

  • What do I need for using Inoyu?

You need a running Apache Unomi server and Claude Desktop installed on your machine with proper configurations set up.

  • Can Inoyu manage multiple users?

Yes, it can handle multiple user profiles through email identification, ensuring consistent context management.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
-
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago