MCP.so
ログイン

Spresh Spy On Competitor Fb Ads MCP Server

@PrashantBtkl

基本情報

カテゴリ

その他

トランスポート

stdio

作者

PrashantBtkl

投稿者

Prashant Bhatkal

Spresh Spy On Competitor Fb Ads MCP Server について

meta ads competitor research claude agent mcp

#marketing#adlibrary#adspy

Spresh Spy On Competitor Fb Ads MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "spreshapp": {
      "command": "npx",
      "args": [
        "-y",
        "spreshapp-mcp"
      ]
    }
  }
}

Spresh Spy On Competitor Fb Ads MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is Spresh Spy On Competitor Fb Ads?

Spresh Spy On Competitor Fb Ads is an MCP server that connects Claude (Desktop or Code) to SpreshApp’s Facebook ad intelligence platform. It lets you research competitors, decode winning ad angles, track brand ad history, and analyze your saved ad library directly from Claude.

How to use Spresh Spy On Competitor Fb Ads?

Install with npx -y spreshapp-mcp and configure it in claude_desktop_config.json for Claude Desktop, claude mcp add for Claude Code, or VS Code’s MCP extension. Authenticate once via npx -y spreshapp-mcp login (OAuth with PKCE) or use an API key for headless environments. After login, you can invoke any of the ad, brand, or library tools via Claude prompts.

Key features of Spresh Spy On Competitor Fb Ads

  • Search Facebook ads by keyword, niche, or industry
  • Run AI analysis on single ads or batches
  • Chat with Claude about an ad’s creative strategy
  • Browse brand profiles, ad history, and active ads
  • Track brands and manage your saved ad library
  • Supports browser OAuth and API key authentication

Use cases of Spresh Spy On Competitor Fb Ads

  • Find high-performing Facebook video ads in a specific niche
  • Research a competitor’s current ad strategy and themes
  • Analyze creative hooks from your saved “Inspiration” folder
  • Track a brand’s ad history over the last 30 days

よくある質問

1

What are the runtime requirements?

Node.js version 20 or higher is required. You also need a SpreshApp account.

2

How does authentication work?

Authentication can be done via OAuth 2.0 with PKCE using the browser-based `login` command, or by providing an API key (starting with `sk_sprs_`) set in the `SPRESHAPP_API_KEY` environment variable. Credentials are saved locally to `~/.spreshapp/credentials.json`.

3

Where are credentials and data stored?

After OAuth login, credentials are saved to `~/.spreshapp/credentials.json` with file mode 600. No other user data storage location is specified.

4

Are there usage limits?

Yes. The README mentions a daily quota that resets at midnight UTC; if reached, you see a “Daily limit reached” error. Some features may not be available on your current plan.

5

What transports and auth methods are supported?

The server uses standard MCP transport via `stdio`. Authentication supports OAuth 2.0 with PKCE (browser-based) and API keys (for headless/remote agents).

コメント

「その他」の他のコンテンツ