- Appcharge launches its hosted MCP server, opening the Appcharge DTC platform to MCP-compatible clients including Claude, Cursor and Claude Code
- The first release exposes several APIs, including Player Authentication, Web Store Personalization and Awarding APIs – the three integration surfaces publisher R&D teams configure first
- A Developer Setup Skills Suite walks teams through callback URL configuration end-to-end, replacing what used to be a manual, support-heavy onboarding cycle
Appcharge released its hosted Model Context Protocol (MCP) server. The new endpoint opens the Appcharge platform directly to MCP-compatible clients such as Claude, Cursor, and Claude Code, and lays the foundation for a broader set of agentic publisher workflows on the platform.
The launch comes as DTC monetization has moved from experimentation to core infrastructure for mobile game publishers. Appcharge has processed more than $1 billion in annualized DTC transactions across more than 150 games, including titles from King, Huuuge, Tripledot, Product Madness, Sciplay, and KamaGames.
With leading publishers now scaling DTC to 30%+ of total revenue, technical onboarding has become one of the biggest gates to faster time-to-value – exactly the problem the new MCP server is designed to remove.
Appchargeʼs hosted MCP server lets publisher R&D teams connect from their preferred MCP-compatible client, such as Claude desktop, Cursor, and Claude Code. Once connected, developers can read configuration, identify missing or invalid callback URLs, and configure the required APIs without leaving their editor. Every action is schema-validated and logged in the Appcharge dashboard.
The first release ships with a focused Developer Setup Skills Suite covering the APIs publishers integrate first, such as Player Authentication, Web Store Personalization, and Awarding. The skills walk teams through implementing or identifying the right callback URLs, configuring them through the API, and validating them end-to-end. The result is a self-service onboarding flow that replaces what was previously a manual, support-heavy cycle.
“The MCP server is the first step in opening Appcharge to the way publisher teams will work next – from inside their IDE, alongside their agents, with every action auditable. We started with onboarding because thatʼs where R&D time gets lost on the integration side. More of the platform will follow from here. ˮ
The MCP server is available today to all Appcharge publishers. For more details, you can visit here. Additional API coverage and dedicated agentic workflows are planned through 2026.
