
This wraps the StupidAPIs press release generation endpoint and exposes a single tool that transforms raw announcements into formatted press releases with headlines, body copy, boilerplate, and media contact sections. You'll need an X-API-Key to authenticate. It's part of the broader Pipeworx gateway ecosystem, which connects to 250+ data sources, so you can either use this standalone endpoint or connect to the full gateway for wider access. Useful when you need to quickly turn internal announcements or product updates into PR-ready copy without manual formatting. The ask_pipeworx natural language interface lets you make requests in plain English rather than calling tools directly.
press-release MCP — wraps StupidAPIs (requires X-API-Key)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
press_release_generate | Transform any announcement into a satirical press release. Accepts announcement text, optional company name, location, and tone (visionary/disrupting/humbled/transparent/pivoting); returns formatted release with headline, body, boilerplate, and media contact section. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"press-release": {
"url": "https://gateway.pipeworx.io/press-release/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/press-release/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 Press Release data" })
The gateway picks the right tool and fills the arguments automatically.
MIT