Emojikey (via Supabase)▌
by identimoji
Emojikey (via Supabase) stores and retrieves LLM interaction styles, ensuring consistent personalized experiences for ev
Integrates with Supabase to persist and retrieve LLM interaction styles using emojikeys, enabling consistent personalized experiences across conversations.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / AI assistants maintaining personalized conversation styles
- / Multi-device AI interactions with consistent context
- / Building AI relationships that persist over time
capabilities
- / Store emoji-based memory keys for AI interactions
- / Retrieve conversation context across sessions
- / Maintain consistent AI personality styles
- / Sync interaction preferences across devices
what it does
Stores emoji-based memory keys in Supabase to help AI assistants maintain consistent interaction styles and remember relationship context across conversations.
about
Emojikey (via Supabase) is a community-built MCP server published by identimoji that provides AI assistants with tools and capabilities via the Model Context Protocol. Emojikey (via Supabase) stores and retrieves LLM interaction styles, ensuring consistent personalized experiences for ev It is categorized under ai ml.
how to install
You can install Emojikey (via Supabase) in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Emojikey (via Supabase) is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
mcp-server-emojikey
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.
Emojikeys are stored online, so you can use them across devices and applications. No user information is stored other than the emojikeys.
Building and Running
There are multiple ways to build and run the server:
Quick Start (Recommended)
# Install dependencies
npm install
# Build the project (all TypeScript errors fixed)
npm run build
# Run the server (coding features disabled by default)
npm run start
# Optional: Run with coding features enabled
CODE_MODE=true npm run start
Alternative Build Options
For more build options, see BUILD_OPTIONS.md which includes:
- Standard Build with Coding Features Disabled (recommended)
- Full Build with All Features (if you need coding dimensions)
- Simplified Build without Coding Files (alternative stable option)
📝 Note Usage note: The first time you use the tool in Claude desktop, tell Claude to "Set emojikey" then next time you start a conversation, he will automatically use this key. You can ask to set vibe, or show emojikey history as well. Have fun!
⚠️ Warning This is a beta version, more features are planned, so the API may change.
Usage with Claude Desktop
Get your API key from emojikey.io and add this to your config:
{
"mcpServers": {
"emojikey": {
"command": "npx",
"args": ["-y", "@identimoji/mcp-server-emojikey"],
"env": {
"EMOJIKEYIO_API_KEY": "your-api-key-from-emojikey.io",
"MODEL_ID": "Claude-3-7-Sonnet",
"CODE_MODE": "false" // Set to "true" to enable coding features
}
}
}
}
Note: The -y flag in the args array tells npx to skip confirmation prompts when installing packages.
Config locations:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
First-time usage: Tell Claude to "Set emojikey". On subsequent conversations, Claude will automatically use this key to maintain context.
Emojikey Initialization Display
When initializing a conversation, the server now displays:
- Starting Key - The most recent key or baseline key if no history exists
- Aggregated Keys - Time-based summaries of your emojikey history:
- Lifetime - Aggregated key from all your previous conversations
- 90-day - Aggregated key from the past 90 days (if available)
- 30-day - Aggregated key from the past 30 days (if available)
- 7-day - Aggregated key from the past 7 days (if available)
- 24-hour - Aggregated key from the past 24 hours (if available)
- Conversation ID - Used for tracking keys within each conversation
Environment Variables
You can customize the behavior with these environment variables:
EMOJIKEYIO_API_KEY- Your API key from emojikey.ioMODEL_ID- The Claude model ID (e.g., "Claude-3-7-Sonnet")CODE_MODE- Set to "true" to enable coding dimensions (disabled by default, may show safe-to-ignore integration warnings)SUPABASE_URL- Custom Supabase URL (optional)SUPABASE_ANON_KEY- Custom Supabase anonymous key (optional)
Tools
initialize_conversation- Get current emojikey at start of conversationget_emojikey- Retrieve current emojikey when requestedset_emojikey- Create and store a new emojikeycreate_superkey- Create a compressed superkey (after 10 regular emojikeys)get_emojikey_history- View previous emojikeys
New in v0.3.1: Coding Context Support
This version includes special dimensions for tracking programming-related interaction patterns:
- 💻🔧 (ImplementationFocus) - Balance between high-level design and implementation details
- 🏗️🔍 (CodeScope) - Building new features vs. improving existing code
- 🧩🧠 (ProblemSolving) - Practical vs. analytical approaches to coding problems
- 🔄📊 (ProcessVsResults) - Emphasizing coding process vs. outcomes
- 📚🧪 (LearnVsApply) - Teaching programming concepts vs. applying them
- 🚀🛡️ (SpeedVsSecurity) - Development speed vs. security considerations
- 👥💻 (CollaborationStyle) - Solo coding vs. collaborative approaches
- 🧬🎨 (CodeStructuring) - Systematic vs. creative code organization
- 📦🔧 (AbstractionLevel) - Preference for abstraction vs. concrete implementations
- 🐞📚 (DebugApproach) - Practical vs. theoretical debugging approaches
These dimensions help Claude adapt to your programming style, providing the right balance of theoretical explanations and practical guidance.
Example Coding Emojikey
[ME|💻🔧8∠45|🧩🧠7∠60|🐞📚6∠40]~[CONTENT|🏗️🔍9∠30|📚🧪8∠65]~[YOU|👥💻7∠70|🧬🎨8∠55]
This shows Claude positioning itself with a balanced implementation focus and somewhat analytical problem-solving approach, while perceiving the user as preferring collaborative coding with creative structuring.
Angle Distribution and Dimension Balance
Emojikey angles represent positioning on each dimension:
- 0° represents one extreme of a dimension
- 90° represents a balanced center position
- 180° represents the opposite extreme
The current implementation assigns angles primarily in the 0-90° range. Future updates will improve angle distribution to better utilize the full 0-180° spectrum, providing more nuanced dimension positioning.
Superkeys
After creating 10 regular emojikeys, Claude will be prompted to create a superkey that compresses their meaning into a single key with format: [[×10emoji-sequence]]
This allows Claude to maintain a longer conversation history context.
⚠️ This is a beta version; the API may change in future updates.
FAQ
- What is the Emojikey (via Supabase) MCP server?
- Emojikey (via Supabase) is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Emojikey (via Supabase)?
- This profile displays 66 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.6 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.6★★★★★66 reviews- ★★★★★Lucas Taylor· Dec 28, 2024
I recommend Emojikey (via Supabase) for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Benjamin Malhotra· Dec 20, 2024
Emojikey (via Supabase) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Chaitanya Patil· Dec 16, 2024
Emojikey (via Supabase) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Nikhil Smith· Dec 16, 2024
We evaluated Emojikey (via Supabase) against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★James Robinson· Dec 8, 2024
According to our notes, Emojikey (via Supabase) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Zaid Kapoor· Nov 27, 2024
Emojikey (via Supabase) has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Min Brown· Nov 19, 2024
Strong directory entry: Emojikey (via Supabase) surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Jin Iyer· Nov 11, 2024
According to our notes, Emojikey (via Supabase) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Piyush G· Nov 7, 2024
According to our notes, Emojikey (via Supabase) benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Emma Jain· Nov 7, 2024
We wired Emojikey (via Supabase) into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 66