Spresh MCP Server

Spresh MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Search Facebook ads, decode competitor creative strategy, and track brand ad history.

What you get

MCP server that connects Claude to SpreshApp's Facebook ad intelligence platform.

Setting it up

The server ships on npm as spreshapp-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

What the assistant can call

Once Spresh is connected, these are the calls the assistant has available:

• ad_search — Search Facebook ads by keyword, niche, or industry
• ad_search_expand_query — Expand a search query to surface more relevant ads
• ad_get — Fetch full details for a specific ad
• ad_get_analysis — Retrieve saved AI analysis for an ad
• ad_analyze — Run AI analysis on any ad
• ad_analyze_batch — Analyze multiple ads in one call
• ad_chat — Chat with Claude about an ad's creative strategy
• brand_search — Search for brands in SpreshApp
• brand_get_overview — Get a brand's full profile and stats
• brand_get_status — Get the current tracking status for a brand
• brand_get_ad_history — Get historical ad volume data for a brand
• brand_list_active_ads — List all ads a brand is currently running

Configuration and credentials

You will need 4 environment variables: SPRESHAPP_API_KEY, SPRESHAPP_ACCESS_TOKEN, SPRESHAPP_REFRESH_TOKEN, SPRESHAPP_CLIENT_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js >= 20 - A SpreshApp account

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Spresh.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the spresh mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Spresh's toolset — ad_search, ad_search_expand_query, ad_get and 11 more — is a fair guide to whether it matches your workflow. It is maintained by PrashantBtkl; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.