> **Community source release (MIT).** Self-host using your own credentials. No NabuxAI production accounts or hosted-service access are included.

# Snapchat Ads MCP by Nabux

Read-only multi-user MCP gateway for the official Snapchat Marketing API.

Production target: `https://snap.nabuxai.com`  
MCP endpoint: `https://snap.nabuxai.com/mcp`

Snap itself also operates the official Snap Ads MCP at:

```text
https://mcp.snapchat.com/ads
```

The Nabux gateway does not claim to replace or proxy that Snap-hosted MCP. It exists to give the Nabux social stack a uniform hosted multi-user credential vault, local retention/search, Account Keys and service-to-service integration while calling Snap's official Marketing API directly.

## Read-only policy

The current Nabux Snapchat tool surface intentionally exposes reads only. There is no generic POST/PUT/DELETE tool and `snapchat_api_get` only permits GET against the configured `https://adsapi.snapchat.com/v1` base.

## MCP tools

- `snapchat_accounts`
- `snapchat_me`
- `snapchat_organizations`
- `snapchat_adaccounts`
- `snapchat_members`
- `snapchat_campaigns`
- `snapchat_adsquads`
- `snapchat_ads`
- `snapchat_creatives`
- `snapchat_invoices`
- `snapchat_stats`
- `snapchat_search_cached_data`
- `snapchat_api_get`

## OAuth

Create the OAuth app in Snap Business Manager and use scope:

```text
snapchat-marketing-api
```

Authorization URL:

```text
https://accounts.snapchat.com/login/oauth2/authorize
```

Token/refresh URL:

```text
https://accounts.snapchat.com/login/oauth2/access_token
```

Nabux callback:

```text
https://snap.nabuxai.com/snapchat/callback
```

Access tokens are short-lived and refresh tokens are encrypted at rest. The gateway refreshes an access token before an authenticated API read when it is close to expiry.

## Data collection

Retrieved organizations, ad accounts, campaign structures, ads, creatives, members and invoices can be retained in the tenant-isolated cache and searched. Stats are returned live from the official Marketing API. This is API-backed advertising data collection, not Snapchat Web/mobile scraping.

## Coolify

Deploy branch `feature/snapchat-mcp-gateway` with `docker-compose.coolify.yml`, routing `snap.nabuxai.com` to port 8000.

Required environment:

```text
PUBLIC_BASE_URL=https://snap.nabuxai.com
APP_SECRET_KEY=<32+ random chars>
SNAP_CLIENT_ID=<Snap Business OAuth app client id>
SNAP_CLIENT_SECRET=<Snap Business OAuth app client secret>
SNAP_REDIRECT_URI=https://snap.nabuxai.com/snapchat/callback
INTERNAL_SERVICE_TOKEN=<random service token>
```

## Status

Production-shaped, read-only implementation. Real E2E requires a Snap Business OAuth app, a user with authorized Organization/Ad Account access, the exact redirect URI, and HTTPS/DNS deployment.