The analysis tools are the difference from scrolling the ad library yourself: an ad can be analysed alone or in a batch, and the results pulled back later, so a brand's whole active set can be worked through in one pass. Following a brand and reading its ad history turns a one-off look into something you can return to.
A Node server over SpreshApp's Facebook ad intelligence platform: ad search and analysis, brand ad history and status, and your own saved ad library organised by folder and tag.
- Facebook ads searched, with query expansion for when the literal terms come back thin
- One ad analysed, or a batch of them, with the analysis fetched back afterwards
- A conversation held about a specific ad
- Brands searched, followed, and read as an overview, a status and a full ad history
- The ads a brand is currently running
- Your saved library reached by folder and tag, and the pages you track
Node.js 20 or newer, and a SpreshApp account. Authenticate once with `npx -y spreshapp-mcp login`, which opens a browser for OAuth with PKCE and saves credentials to `~/.spreshapp/credentials.json`. For headless setups use an API key instead — keys start with `sk_sprs_` and go in the environment.
One command plus a key — npx -y spreshapp-mcp, then supply credentials