mcp-dostuff
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-dostuffwhat events are happening in Austin?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-dostuff
DoStuff network MCP.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
Tool | Description |
| List the metros DoStuff covers (slug + name). Pass a slug to the events tool. |
| Curated things-to-do / events for a DoStuff metro. Defaults to today; pass |
Related MCP server: Evento Public MCP Server
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"dostuff": {
"url": "https://gateway.pipeworx.io/dostuff/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/dostuff/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 Dostuff data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Search events, conference weeks, cities, venues and artist schedules via remote MCP.
Google Events listings with dates, venues, and ticket links via a hosted MCP server.
PredictHQ MCP — wraps the PredictHQ Events API (predicthq.com)
Access U.S. congressional data - bills, votes, members, committees - via MCP.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceInteract with the Cooper Hewitt API with MCP.2MIT
- FlicenseAqualityDmaintenanceMCP server to list and get events from Evento's public API using an API key.21-
- AlicenseNot gradedqualityCmaintenanceEnables querying Washington DC open data from opendata.dc.gov and ArcGIS REST API through MCP.6 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Skiddle events by ID and listing event categories. Part of Pipeworx MCP gateway.8 npmMIT