Skip to main content
Glama
pipeworx-io

mcp-emoji

by pipeworx-io

mcp-emoji

Emoji MCP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool

Description

emoji_lookup

Look up an emoji by :shortcode: (e.g. ":fire:" or "fire") to get the character + keywords, OR pass an emoji character to get its shortcode/name. Keyless, offline.

search_emoji

Search emoji by keyword/name (e.g. "party", "money", "animal") and return matching emoji with shortcodes. Keyless, offline.

Related MCP server: mcp-unicode

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "emoji": {
      "url": "https://gateway.pipeworx.io/emoji/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/emoji/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Emoji data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/emoji_lookup \
  -H 'Content-Type: application/json' \
  -d '{"input":":fire:"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/emoji_lookup. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables looking up HTTP status codes (100-599) with reason phrases, categories, and meanings, and listing statuses filtered by class, all offline and without keys.
    5 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides tools to inspect Unicode characters, escape/unescape strings in various formats (JS, HTML, URL), all offline and keyless.
    43 npm
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    Provides technical SEO tools for AI agents, including structured data generation, meta tag creation, robots.txt validation, and SERP previews, all offline with no API key or account.
    18
    22 PyPI
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables emoji lookup by category and group, including random emoji selection, using the free EmojiHub API without authentication.
    4 npm
    MIT