
This wraps the Giphy API so you can search and retrieve GIFs directly from Claude or other MCP clients. It's part of the Pipeworx gateway, which means you can either connect to the standalone Giphy endpoint or get it bundled with 673+ other data sources through the main gateway. Ships with a public beta key so you can start using it immediately without API setup. You can call tools directly or use the ask_pipeworx natural language interface to search for GIFs by describing what you want. Good for adding visual content to workflows, building chat interfaces, or just quickly grabbing reaction GIFs without leaving your editor.
Giphy MCP — wraps Giphy API (public beta key, free)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
search_gifs | Search Giphy for GIFs by keyword. Returns title, URL, rating, and multiple image sizes. |
trending_gifs | Get currently trending GIFs on Giphy. Returns title, URL, rating, and multiple image sizes. |
random_gif | Get a random GIF, optionally filtered by tag (e.g., "cats"). Returns title, URL, rating, and image URLs. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"giphy": {
"url": "https://gateway.pipeworx.io/giphy/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/giphy/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 Giphy data" })
The gateway picks the right tool and fills the arguments automatically.
MIT