Emoji

Emoji — connector documentation

• MCP endpoint: https://emoji.connectorbay.com/mcp
• REST API: POST https://emoji.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://emoji.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://emoji.connectorbay.com/health · Tool schemas: https://emoji.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/emoji · agent@connectorbay.com

What Emoji is for

"What's the shortcode for the fire emoji?", "find me an emoji for a birthday message", "does the wave emoji have skin-tone versions?", "turn this sentence into emoji" — answered instantly from a bundled reference built from Unicode's own emoji data, with no live lookup and nothing sent anywhere.

What it does

emoji_search finds emoji by a name, keyword, or category substring, ranked by relevance; emoji_lookup returns full detail — name, codepoint, category, subgroup, keywords, shortcode, and whether it supports skin tones — for a literal character, a name, or a shortcode. emoji_by_category lists every emoji in one Unicode group (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), and category_list gives every category with its count. random_emoji returns one at random, optionally scoped to a category. shortcode_lookup resolves a GitHub/Slack-style :shortcode: (:joy:, :thumbsup:, :+1:) to its emoji; emoji_to_shortcode does the reverse. skin_tone_variants lists the actual Fitzpatrick light-through-dark variant characters for emoji that support them. text_to_emoji is a fun, best-effort word-by-word translator for a short phrase, built entirely from this connector's own keyword index. emoji_combo_search suggests a small curated set of emoji (3-6) for a mood or theme — birthday, celebration, sad, love, and about 15 more.

Where the data comes from

Every emoji's codepoint, official name, Unicode group/subgroup, and introduction version comes from Unicode's own public emoji-test.txt (plain-text CLDR ordering data — never artwork). Shortcode aliases (the GitHub/Slack-style names like :joy: or :thumbsup:) are layered on top from the open-source PyPI emoji package's alias table, used only once at build time to produce this connector's bundled data/emoji.json — it is not a runtime dependency, and the two are unrelated projects that happen to share a name. 1,887 emoji across 9 categories are bundled as of this build.

What it is not

Not a picture library — every "emoji" here is a Unicode character (text), the same character your own device already knows how to render in its own native style; Emoji doesn't ship or reproduce any platform's copyrighted emoji artwork. It's also not live: a brand-new emoji from a Unicode release after this bundle's build date won't show up until the data is rebuilt, and text_to_emoji / emoji_combo_search are playful best-effort helpers, not a precision translation tool.

Tools

Search & lookup

emoji_search — Search all bundled emoji by name, keyword, shortcode, or category substring, ranked by relevance. Use for "find an emoji for birthday", "search emoji for cat". Args: query, limit.

emoji_lookup — Full detail for one emoji — name, codepoint, category, subgroup, keywords, shortcode, and whether it supports skin-tone modifiers — looked up by the literal character, its name, or a shortcode. Use for "what is 🥲 called", "look up the emoji named shrug". Args: emoji_or_name.

Browse

emoji_by_category — Every emoji in one Unicode category/group. Use for "list all food emoji", "show me every flag emoji". Args: category.

category_list — Every available emoji category with how many emoji are in each. Use for "what emoji categories are there".

random_emoji — One random emoji, optionally scoped to a category. Use for "give me a random emoji", "pick a random animal emoji". Args: category.

Shortcodes

shortcode_lookup — Resolve a GitHub/Slack-style :shortcode: to its emoji and full detail. Use for "what emoji is :joy:", "what does :fire: look like". Args: shortcode.

emoji_to_shortcode — The reverse of shortcode_lookup: given a literal emoji character, its primary and alternate GitHub/Slack-style shortcodes. Use for "what's the shortcode for 🔥", "how do I type this emoji on Slack". Args: emoji.

Fun

skin_tone_variants — For emoji that support Fitzpatrick skin-tone modifiers, the actual variant characters from light through dark. skin_tone_capable: false if the emoji has no tone variants. Use for "does the wave emoji have skin tones", "show me the thumbs up in different skin tones". Args: emoji.

text_to_emoji — A fun, best-effort word-by-word emoji translator for a short phrase, using this connector's own keyword index — no external API. Words with no good match are skipped. Use for "translate this sentence into emoji", "turn this into emoji". Args: text.

emoji_combo_search — A small curated set of emoji (3-6) that together represent a mood or theme — birthday, celebration, sad, love, congratulations, and about 15 more. Use for "emoji for a birthday message", "give me some sad emoji", "emoji combo for a party invite". Args: mood_or_theme.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/emoji/support

Emoji — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Emoji is. Emoji is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local emoji reference and search tool. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — a search term, an emoji character, a name, a shortcode, or a short phrase to translate — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled data file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Emoji is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Emoji — Terms of Service

Effective 24 September 2026. These terms govern use of the Emoji connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Emoji is a fully local emoji reference and search tool — search, exact lookup, category browsing, shortcode resolution both ways, skin-tone variants, a text-to-emoji translator, and mood/theme combos — built from data bundled at build time. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Not official, not real-time. Emoji is an independent reference tool, not affiliated with or endorsed by the Unicode Consortium, any platform vendor, or any other party. It reflects the Unicode emoji release current as of this Service's own build date; a very recently released emoji may not yet be included.
3. Text, not artwork. Every emoji returned is a Unicode character (text) — the same character your own device renders in its own native style. The Service does not provide or reproduce any platform's emoji artwork or images.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled data file, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/emoji

Emoji support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://emoji.connectorbay.com/mcp
• REST API: https://emoji.connectorbay.com/openapi.json
• Live status: https://emoji.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Emoji never asks for them.