mcp -emojikey

This MCP server collects and persists emoji-based memory keys (emojikeys) to help Claude maintain consistent interaction styles and remember relationship context across conversations. It uses your emojikey.io API to generate and manage keys, and stores derived data in a configurable backend. Tools exposed by the server include initialization and retrieval of the current emojikey, creation of new emojikeys, generation of a compressed superkey after enough history, and viewing emojikey history. To use it, configure the server in your Claude Desktop setup and start the MCP server through the Node/npm workflow described in the installation section. When you start a conversation, you can instruct Claude to Set emojikey to initialize context; subsequently Claude will use the emojikey automatically to shape responses and memory. The additional coding context features let you enable specialized dimensions to tailor Claude’s behavior for programming-related interactions.

Prerequisites:

• Node.js installed (v14+ recommended)
• npm or npm per your environment
• Access to emojikey.io API key (and optional Supabase keys for backend)

1. Install dependencies and build

npm install
npm run build

2. Run the server

npm run start

Optional: enable coding features by setting CODE_MODE when starting or via environment:

CODE_MODE=true npm run start

If you prefer a direct npx run without local build, ensure you have access to the @identimoji/mcp-server-emojikey package and run the command shown in the configuration example.

Notes:

• The server expects your EMOJIKEYIO_API_KEY and MODEL_ID to be set as environment variables (or within the mcp config under env).
• If you’re using a custom backend, set SUPABASE_URL and SUPABASE_ANON_KEY accordingly.
• The config is designed to be embedded in Claude Desktop’s MCP config JSON as shown in the mcp_config section.

Tips and caveats:

• The -y flag in the npx args skips installation prompts, enabling seamless first-time setup.
• CODE_MODE toggles coding-related features; enable only if you need programming-aware embeddings and tools.
• Keep your EMOJIKEYIO_API_KEY secure; rotate keys via the emojikey.io dashboard if needed.
• If you don’t specify a backend (SUPABASE_URL/ANON_KEY), the server may fall back to a default or limited storage option depending on the build.
• After initial emojikey setup in Claude, you can ask Claude to reveal or reuse the current emojikey history using provided tools like get_emojikey_history.
• The emojikey system supports a workflow for creating a superkey after 10 regular emojikeys to compress history; this can improve long-term memory efficiency.