Prweb MCP server

@pipeworx/prweb

Live press releases from PRWeb's site-wide "All News Releases" RSS feed — headline, issuer, industry and subject tags, publish time and excerpt, newest first. PRWeb is Cision's small-business wire: issuers are mostly local businesses, nonprofits, agencies and startups rather than listed companies.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

of releases, newest first. newestitemat tells a caller whether the feed is quiet or stalled.

• prweblatestreleases(since_hours?, limit?) — the current rolling window

headline, issuer, excerpt and industry tags, within the current window only.

• prwebsearchreleases(query, limit?) — keyword/company match over

call returned. Fails clearly (not silently empty) if the release has scrolled out of the current window.

• prwebgetrelease(url) — one specific release, matched by the URL a prior

Auth

Keyless. No account, no clickthrough terms. prweb.com/robots.txt does not disallow /rss/.

Data sources

Releases" feed. Measured 2026-09-22: 20 items spanning about 7.5 hours.

• — PRWeb's "All News

Every call re-fetches this same rolling ~20-item window live — it is not an archive. searchreleases only ever searches what is currently in the window and getrelease can miss something that has already fallen out of it (the tool says so explicitly rather than returning an empty result).

Two URL traps met while finding this feed: the legacy /rss2/daily.xml path 301s here, and /rss (no slash) 301s to /rss/, which is a 152 KB HTML index page that answers HTTP 200 — a 200 that is not a feed. That index is rendered client-side, so its per-category feeds are not enumerable from the served HTML and this pack does not read them.

The issuer is pulled from . names PRNewswire itself on every item (PRWeb runs on the PR Newswire platform), so a generic byline reader would mislabel every release.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "prweb": {
      "url": "https://gateway.pipeworx.io/prweb/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/prweb/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/prweb_latest_releases \
  -H 'Content-Type: application/json' \
  -d '{}'

Shortened. The full README is on GitHub.