A hosted marketing MCP server for any AI app

Apps it works with

Any app that adds a remote MCP server by URL (Streamable HTTP) and signs in with OAuth. These say so in their own documentation, checked on 2026-11-02:

• Claude - the V-Kit plugin, with the know-how for each source; Claude Code - the same plugin from the terminal. See Install.
• ChatGPT - the V-Kit plugin from ChatGPT Plugins, any plan. See Install.
• Cursor - add the server by its URL; Cursor signs in with OAuth.
• VS Code with GitHub Copilot - add an MCP server from a URL (HTTP) and sign in when it asks.
• Gemini CLI - a remote server by URL; the CLI finds the sign-in and registers itself.
• Mistral Le Chat - Connectors → a custom MCP connector by URL; the sign-in opens in a window.
• Cherry Studio - Settings → MCP → Streamable HTTP; it signs in when you save the server.

DeepSeek and other models

DeepSeek’s own chat app does not connect MCP servers (checked on 2026-11-02). To ask a DeepSeek model about your numbers, use it inside an MCP app that offers DeepSeek models - Cherry Studio, for example - and add V-Kit there. The same works for other models such an app supports: V-Kit answers whichever model calls it.

How to connect

1. In your app, add a remote MCP server (Streamable HTTP) with the address https://marketing-kit.app/mcp and the name v-marketing-kit. Leave the OAuth client ID and secret empty - the app registers itself.
2. Press Connect (or Authenticate), sign in with Google or Meta and press Allow. The sign-in only identifies you.
3. On Connections authorize Meta, Google and TikTok in their own dialogs, connect Google Play and Apple Ads with their own buttons, and save the keys for AppsFlyer, RevenueCat and App Store Connect.
4. Ask in a new chat. A good first message: “check v-marketing-kit status”.

Works in Claude Code

Claude Code uses the same V-Kit connector. Run claude plugin marketplace add arey325/marketing-kit-plugin, then claude plugin install v-marketing-kit@v-marketing-kit. After /reload-plugins, open /mcp → v-marketing-kit → authenticate.

Then connect your sources on Connections and ask in Claude Code. The steps are in the Setup guide.

How the OAuth sign-in works

• Your app calls https://marketing-kit.app/mcp and gets “sign in first” with a link to V-Kit’s OAuth settings, so it finds the sign-in page by itself.
• The app registers itself - dynamic client registration or a client metadata URL - so there is no client ID or secret to paste.
• A browser window opens marketing-kit.app: sign in with Google or Meta, check the name of the app asking for access, press Allow.
• The app receives a token for your account only (OAuth 2.1 with PKCE). It works for an hour and the app renews it by itself; after 90 days without use, sign in again. Your passwords and source keys never reach the app.
• Cut an app off any time under Connections → Connected assistants.
• An app that only accepts a fixed token in a header can’t connect: V-Kit gives MCP apps no static API keys, only this sign-in.

What you can ask

Without the plugin there is no V-Kit know-how in the app, so the model relies on the tool descriptions alone and answers are a little rougher than in Claude or ChatGPT with the plugin.

• “Spend, clicks and conversions by campaign in Meta and Google Ads last week.”
• “Installs by media source in AppsFlyer for the last 7 days.”
• “MRR, trials and churn in RevenueCat this month.”
• “Organic search queries that grew most in Search Console.”
• “Rating and latest reviews of our app in the App Store.”

V-Kit in your own app or agent

Building a product, an internal agent or an automation on top of marketing data? We are preparing an SDK: the same sources, the same sign-in and read-only access, called from your own code instead of a chat.

Request SDK access - tell us what you are building, which sources you need and in which language, and the developer will write back.

Access and privacy

• Read-only, except the changes you confirm in chat (copying AppsFlyer partner-integration settings and turning on App Store Connect Analytics Reports).
• Tokens and keys are encrypted at rest (AES-256-GCM) and never shown back, logged or put into answers.
• Your numbers are fetched when you ask and not stored beyond a 15-minute in-memory cache; large results wait behind a download link for up to 24 hours. See the privacy policy.
• Disconnect a source, remove a key or delete your account on the site at any time.