# Affise MMP MCP Server

> Remote Model Context Protocol server for Affise MMP, the mobile measurement
> and attribution platform. Gives an AI assistant read-only access to a
> customer's raw attribution records — clicks, installs, events and
> conversions — through the Affise MMP reporting API.

Endpoint: https://mcp-mmp.affise.com/mcp
Transport: Streamable HTTP
Protocol revisions: 2026-07-28 and the 2025 legacy family (2025-06-18, 2025-03-26)
Authorization: OAuth 2.0 with PKCE (S256) and Dynamic Client Registration
Surface: read-only — no tool mutates data in the connected account

## Setup

Add as a custom connector in an MCP client (Claude, Cursor, Continue.dev, or
any Streamable HTTP client) using the endpoint above. The client performs the
OAuth flow; the user enters one value — their Affise MMP API key — and every
request is scoped to that key.

## Discovery

- /.well-known/oauth-protected-resource
- /.well-known/oauth-protected-resource/mcp
- /.well-known/oauth-authorization-server
- /health

Scopes: mmp:read, mmp:reports

## Tools

- mmp_ping: confirm the connector can reach the reporting API with the stored key

Raw report tools (clicks, installs, events, conversions) arrive in a later
release.

## Notes for agents

- Every raw-data request needs an explicit time window.
- A rejected API key means the connector must be reconnected with a current
  key; retrying the same call will not help.

## Links

- Affise MMP: https://affisemmp.com
- Customer help center: https://help-center.affisemmp.com/en/
- Report a security issue: support@affise.com, subject starting with SECURITY.
  Never include a live API key or access token in a report.