MCP MCP Server

MCP Server for emojikey.io ... save your unique relationship state and interaction style with your favorite LLM

Local serverstdioTypeScript

What is the MCP MCP server?

MCP MCP server exists for a simple reason — assistants are far more useful when they can act on MCP directly instead of describing what you should do. MCP Server for emojikey.io ... save your unique relationship state and interaction style with your favorite LLM.

What you get

MCP server for persisting LLM relationship context as emoji-based memory keys. This allows Claude to maintain consistent interaction styles and remember relationship context across conversations.

What the assistant can call

Once MCP is connected, these are the calls the assistant has available:

  • MacOS — ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows — %APPDATA%/Claude/claude_desktop_config.json
  • initialize_conversation — Get current emojikey at start of conversation
  • get_emojikey — Retrieve current emojikey when requested
  • set_emojikey — Create and store a new emojikey
  • create_superkey — Create a compressed superkey (after 10 regular emojikeys)
  • get_emojikey_history — View previous emojikeys

Configuration and credentials

You will need 5 environment variables: EMOJIKEYIO_API_KEY, MODEL_ID, CODE_MODE, SUPABASE_URL, SUPABASE_ANON_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Plenty of AI and media services servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — MacOS, Windows, initialize_conversation and 4 more — is a fair guide to whether it matches your workflow. It is maintained by identimoji; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
MacOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%/Claude/claude_desktop_config.json
initialize_conversationGet current emojikey at start of conversation
get_emojikeyRetrieve current emojikey when requested
set_emojikeyCreate and store a new emojikey
create_superkeyCreate a compressed superkey (after 10 regular emojikeys)
get_emojikey_historyView previous emojikeys

Configuration

VariableDescriptionRequired
EMOJIKEYIO_API_KEYCredential the server authenticates with.Yes
MODEL_IDConfiguration value read at startup.Optional
CODE_MODEConfiguration value read at startup.Optional
SUPABASE_URLEndpoint or connection string the server talks to.Yes
SUPABASE_ANON_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to MacOS.
  • Use MCP to Windows.
  • Use MCP to initialize conversation.

Frequently asked questions

An emojikey is an emoji-based memory key that stores LLM relationship context, allowing Claude to remember interaction styles and preferences across conversations.