Adversee's MCP server exposes your workspace's competitor data to Claude, Cursor and any client that speaks the Model Context Protocol. You connect with a personal API key; the assistant can only read, and it sees what your role sees.
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 the right tool: competitors, campaigns, events, banner order history, Meta ads and images.
Competitor campaigns with extracted fields (cap, wagering, rate), terms and change history.
New, changed and ended campaigns, banner and Meta events, outages. Full history with date ranges and pagination.
Live and removed banners, desktop and mobile; slider order history tour by tour.
Active and ended ads, Ad Library links and a per-brand coverage note.
Type, category, game group and the game name written on each banner and ad; a confidence-scored campaign suggestion.
Banner and ad images returned as images, so the assistant can see them.
No tool writes data or changes settings.
A key belongs to you and one workspace; it stops working if you leave the team.
Revoke keys from the dashboard in one click; every call is written to an audit log.
60 requests per minute per key; the plain key is never stored, only its hash.