Affise MMP MCP server › Other clients
The Affise MMP MCP server implements the open Model Context Protocol over Streamable HTTP, so anything that speaks MCP and can run an OAuth sign-in can use it.
Before you start
Any MCP client that supports remote servers with OAuth, and your Affise MMP API key.
{
"mcpServers": {
"affise-mmp": {
"type": "http",
"url": "https://mcp-mmp.affise.com/mcp"
}
}
}Clients that support OAuth prompt you to sign in on first use.mcp-remote:{
"mcpServers": {
"affise-mmp": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp-mmp.affise.com/mcp"]
}
}
}mcp-remote opens the sign-in in your browser and keeps the token on your machine.401 and a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource.Ask your client for yesterday’s installs by partner. A healthy connection returns real numbers from your Affise MMP account.
Authorization header afterwards. The hosted endpoint accepts OAuth tokens only — there is no static bearer token.429 response carries a ratelimit-reset header with the seconds left in the current window.Once you are connected, these are good first questions. See more examples or the full tool reference.