
Wraps the EmojiHub API to pull random emoji data into your MCP workflow. Exposes a single tool, random_emoji, that returns character, name, category, and group for an unpredictable emoji. No authentication required. Runs through Pipeworx's gateway infrastructure, which also offers an ask_pipeworx natural language interface if you'd rather skip direct tool calls. Useful when you need emoji variety for testing UI, generating placeholders, or adding visual elements without hardcoding a list. The API is simple enough that you're really just trading setup time for convenience here.
EmojiHub MCP — wraps EmojiHub API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
random_emoji | Get a random emoji with its character, name, category, and group. Use when you need an unpredictable emoji for variety or surprise elements. |
get_by_category | Search emojis by category (e.g., "smileys-and-people", "food-and-drink", "travel-and-places", "symbols"). Returns matching emojis with names and groups. |
get_by_group | Search emojis by group (e.g., "face-positive", "face-negative", "animals-mammal", "hand-fingers-open"). Returns matching emojis with names and categories. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"emojihub": {
"url": "https://gateway.pipeworx.io/emojihub/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/emojihub/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.
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 Emojihub data" })
The gateway picks the right tool and fills the arguments automatically.
MIT