ad_searchLABSCO SUMMARY
Competitor ad research, run as a conversation instead of a browse.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
One command — npx -y spreshapp-mcp
USE CASES
01
Working out what a competitor is running right now
Search the brand, then list the ads it currently has live.
02
Understanding why an ad works
Analyse the ad and read the analysis back, or talk about it directly.
03
Finding ads on an angle rather than a name
Search the ad set, and expand the query when the literal terms return too little.
04
Watching a brand over months
Follow it, then read the ad history and status rather than re-searching each time.
05
Getting through a batch of saved ads
Analyse them as a batch and pull the results as they finish.
06
Using the library you already built
Reach saved ads through their folders and tags instead of searching from scratch.
18 tools
Listed in project docs. Your client may show a different list.
ad_search_expand_queryad_getad_get_analysisad_analyzead_analyze_batchad_chatbrand_searchbrand_get_overviewbrand_get_statusbrand_get_ad_historybrand_list_active_adsbrand_followsearch_adsget_folder_adslist_foldersget_tagsget_pagesBEFORE YOU INSTALL
What to know first
Tools you get
18 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js >= 20
Optional
SPRESHAPP_API_KEY in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y spreshapp-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"spreshapp": {
"command": "npx",
"args": [
"-y",
"spreshapp-mcp"
]
}
}
}No key is needed if you sign in once with npx -y spreshapp-mcp login: it opens a browser and saves your credentials to ~/.spreshapp/credentials.json. For headless setups, create a key at spreshapp.com/app/api-access (keys start with sk_sprs_) and set SPRESHAPP_API_KEY in the server's environment — in a client entry, its env block. The README's example: SPRESHAPP_API_KEY=sk_sprs_... npx -y spreshapp-mcp.
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add spreshapp -- npx -y spreshapp-mcpNo key is needed if you sign in once with npx -y spreshapp-mcp login: it opens a browser and saves your credentials to ~/.spreshapp/credentials.json. For headless setups, create a key at spreshapp.com/app/api-access (keys start with sk_sprs_) and set SPRESHAPP_API_KEY in the server's environment — in a client entry, its env block. The README's example: SPRESHAPP_API_KEY=sk_sprs_... npx -y spreshapp-mcp.
VS Code
VS CODE · JSON
{
"servers": {
"spreshapp": {
"command": "npx",
"args": [
"-y",
"spreshapp-mcp"
]
}
}
}No key is needed if you sign in once with npx -y spreshapp-mcp login: it opens a browser and saves your credentials to ~/.spreshapp/credentials.json. For headless setups, create a key at spreshapp.com/app/api-access (keys start with sk_sprs_) and set SPRESHAPP_API_KEY in the server's environment — in a client entry, its env block. The README's example: SPRESHAPP_API_KEY=sk_sprs_... npx -y spreshapp-mcp.
