Adversee's MCP server exposes your workspace's competitor data to Model Context Protocol clients such as Claude and Cursor. You connect with a personal API key; the assistant reads, and if your role allows it makes limited edits such as assigning a campaign category or adding a social account to a competitor. The key belongs to you and your workspace and works for as long as you are on the team.
What changed in competitors' homepage banners this week?
adversee_list_events {"tip":"banner_eklendi","baslangic":"…"}{
"hareketler": [
{ "id": "…", "tip": "banner_eklendi", "baslik": "…", "rakip": "Rakip A",
"rakipSlug": "rakip-a", "seviye": "hamle", "zaman": "2026-10-07T10:00:12.318Z",
"kampanyaId": null,
"ayrinti": { "gorunum": "mobil", "slideId": "…", "gorselId": "…", "url": "https://…" } }
],
…There's one banner move this week: Rakip A added a new banner to its mobile homepage. Want me to open the image with adversee_get_image?
In the dashboard, go to Settings (Ayarlar) > API (MCP) and name your key. It is shown only once; copy it and keep it safe.
One command for Claude Code; ready-made config snippets for Cursor and Claude Desktop in the dashboard and in the docs.
The assistant picks tools based on their descriptions: competitors, campaigns, events, banner order history, Meta ads and images.
Competitor campaigns with extracted fields (cap, wagering, rate), terms, last seen, removal detection and change history.
New, changed and ended campaigns, banner and Meta events, competitors' new social media posts, outages. Full history with date ranges and pagination.
Live and removed banners, desktop and mobile; banner order history scan run by scan run, up to 366 days.
Active and ended ads, Ad Library links and a per-brand coverage note.
For every classified banner and ad: type, category, game group and the game name written on it; a confidence-scored campaign suggestion; the confirmation status of the campaign and game match (candidate, confirmed, rejected) and who confirmed it.
Banner and ad images returned as images; in clients that support images, the assistant can see them.
Competitor push and SMS messages captured by the Notification Bridge, with each receipt time.
Last scan run, last successful scan run and open faults per competitor and surface: how fresh the data is.
The assistant acts with your current role: viewers can only read. Write tools never delete competitors, accounts or categories, and never change settings (replacing a social account or closing a Meta page you added stops that follow; the content stays); every write is logged with its before and after state, and most writes can be undone within 24 hours if the record has not changed since.
A key belongs to you and your workspace; it works for as long as you are on the team.
Revoke keys from the dashboard in one click; the Owner and Admin roles can see and revoke the team's keys. Every call is written to an audit log, kept for 180 days.
60 requests per minute per key; writes are further limited to 10 per minute per key, 50 per hour per user and 100 per hour per workspace. The plain key is never stored; only its hash and its first 10 characters, for display, are kept.