Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.appcharge.com/llms.txt

Use this file to discover all available pages before exploring further.

The Appcharge Model Context Protocol (MCP) server connects MCP-compatible AI clients to Appcharge data and operations. Use it to check and manage technical setup tasks in the Publisher Dashboard, such as callback and webhook URL configuration. The server supports SSE transport and works with MCP-compatible tools such as Cursor, Claude, and Claude Code.
The MCP server doesn’t expose secrets, tokens, player-level data, payment data, internal logs, or unrelated publisher configuration.

​
Before you begin

Make sure you have:
  • An MCP-compatible AI client that supports remote MCP servers over SSE.
  • Your Appcharge Publisher Token.
  • Access to the relevant Publisher Dashboard account.

​
Connect to the MCP server

To connect the Appcharge MCP server to your AI client:
  1. Open your MCP-compatible client.
  2. Add a new remote MCP server.
  3. Add the Appcharge MCP server configuration to your MCP JSON file: 
    {
  "mcpServers": {
    "appcharge": {
      "url": "https://mcp.appcharge.com/sse",
      "headers": {
        "x-publisher-token": "{YOUR_PUBLISHER_TOKEN}"
      }
    }
  }
}
  4. Replace {YOUR_PUBLISHER_TOKEN} with your Publisher Token.
  5. Start the connection.
Once connected, your client can call the Appcharge MCP tools that are available for your account.

​
MCP tools

The Appcharge MCP server exposes the following tools.

​
Appcharge integration tools

Instead of configuring your developer settings manually in the Publisher Dashboard, use these tools to streamline your technical onboarding with Appcharge.
Tool nameDescriptionUse case
Get Developer Settings URLsRetrieves your current callback and webhook URL configuration from the Publisher Dashboard.Check which integration URLs are configured, missing, or ready for onboarding validation.
Manage Developer Settings URLsUpdates your callback and webhook URL configuration in the Publisher Dashboard. Omitted fields are left unchanged, and fields set to null are cleared.Configure or update your integration URLs.

​
Example prompts

After you connect the MCP server, try prompts such as: 
Check which of my callback URLs are missing for my account.

Update the Player Authentication callback URL.

Validate my Grant Awards callback URL and tell me what to fix.