
Wraps the Wikimedia Feed API with three straightforward tools: pull Wikipedia's featured article for a given date, grab the most-read articles, or fetch the picture of the day with metadata. No authentication required. Runs as a hosted service through the Pipeworx gateway, so you just point your MCP client at the URL and start querying. Good for adding Wikipedia content feeds to agents without dealing with API calls yourself. Part of a larger gateway that bundles 673+ data sources, but this works standalone if you only need Wikipedia feed data.
Wikifeed MCP — wraps Wikimedia Feed API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
on_this_day | Get historical events, births, deaths, and holidays that occurred on a given month and day across all years. |
featured_article | Get Wikipedia's featured article for a specific date. |
most_read | Get the most-read Wikipedia articles for a specific date. |
picture_of_day | Get Wikipedia's picture of the day for a specific date, including title, description, and image URL. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"wikifeed": {
"url": "https://gateway.pipeworx.io/wikifeed/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/wikifeed/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 Wikifeed data" })
The gateway picks the right tool and fills the arguments automatically.
MIT