mcp-server-emojikey

Emojikey MCP Server

mcp-server-emojikey saves relationship context and interaction preferences as emoji-based memory keys for Claude users. It connects to emojikey.io so stored context can carry between conversations, devices, and applications.

Server facts

mcp-server-emojikey

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
4
Last commit
Data as of

Overview

Emoji-based memory keys give Claude a stored representation of relationship context and conversational style. This project connects that workflow to emojikey.io, where keys remain available across devices and applications. Users begin by asking Claude to set an emojikey. At conversation startup, initialize_conversation retrieves recent context and returns a conversation identifier that subsequent key operations use to keep each conversation’s state separate. The startup display includes a recent or baseline key, historical aggregates where available, and the conversation identifier.

The remaining exposed tools support inspecting and updating that context: get_emojikey retrieves the current key for a vibe check, set_emojikey records a new representation when the interaction changes, and get_emojikey_history lists earlier entries for the conversation. Keys encode dimensions through emoji pairs, magnitudes, and angles. Optional coding dimensions cover preferences such as implementation detail, debugging approach, and collaboration style; coding support is disabled by default. Claude Desktop configuration uses an emojikey.io API key. The project states that only emojikeys are stored as user information and warns that its beta API may change.

mcp-server-emojikey setup notes

  • mcp-server-emojikey records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers