
Wraps the Imgflip API to give Claude access to meme templates and generation capabilities. The free tier lets you list templates without authentication, which is useful for browsing popular formats or programmatically finding the right base image. Hosted via Pipeworx's gateway infrastructure, so you can connect over HTTP without running a local server. If you're building something that needs to generate or reference internet meme formats, this gets you connected to Imgflip's catalog directly from your MCP client. Part of a larger gateway offering 250+ data sources, but this endpoint focuses specifically on Imgflip's API surface.
Imgflip MCP — wraps Imgflip API (free, no auth for template listing)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_memes | Browse the 100 most popular meme templates. Returns template name, image URL, dimensions, and text box coordinates. Use template IDs with caption_image to create memes. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"imgflip": {
"url": "https://gateway.pipeworx.io/imgflip/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/imgflip/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 Imgflip data" })
The gateway picks the right tool and fills the arguments automatically.
MIT