Model Context Protocol (MCP)

The Appcharge Model Context Protocol (MCP) server connects MCP-compatible AI clients to Appcharge data and operations. Use it to manage Publisher Dashboard setup, look up your projects, and search Appcharge documentation without leaving your AI client.

The server supports SSE transport and works with MCP-compatible clients such as Cursor, Claude, and Claude Code. It’s currently available in sandbox, and will soon be available in the production environment.

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.
• Access to your Publisher Dashboard sandbox account. Appcharge uses OAuth to authenticate the MCP server.

Connect to the MCP server

The process for connecting to the MCP server is subject to change. AI clients may update how they configure or connect to MCP servers, so the steps below may vary depending on your client version and settings.

Follow the instructions for your AI client to add and authenticate the Appcharge MCP server. Once connected, your client can call the MCP tools available for your Publisher Dashboard account.

Cursor

To connect the MCP server to Cursor:

1. In Cursor, open Cursor Settings.

2. In the sidebar menu, go to Tools & MCPs, and then click New MCP Server. A JSON file opens with a list of your existing MCP servers.

3. Add and save the Appcharge MCP server configuration to the file:

   {
     "mcpServers": {
       "appcharge-sandbox": {
         "url": "https://api-sandbox.appcharge.com/mcp",
         "timeout": 10000
       }
     }
   }
   

4. Now that it’s installed, you need to log in to the Publisher Dashboard to authorize the Appcharge MCP. To do this, go back to Cursor Settings and click the Connect button next to the Appcharge MCP.

   

5. The browser opens. If you’re not already logged in to the Publisher Dashboard sandbox environment, you’ll be directed to log in. Once authenticated, the browser will prompt you to open Cursor. Click Open Cursor.

6. In Cursor Settings, you should now see that you’re logged in and connected to the Appcharge MCP.

Claude Code

To connect the MCP server to Claude Code:

1. Make sure you have the Claude Code CLI installed.

2. In your terminal, run the following command to add the Appcharge MCP server:

   claude mcp add --transport http appcharge-sandbox https://api-sandbox.appcharge.com/mcp
   

3. Now that it’s installed, you need to authorize the Appcharge MCP. To do this, open Claude Code in the same folder where you ran the CLI command. Then, in the chat panel, ask it to Connect to the Appcharge MCP server, or Authenticate with Appcharge.

4. Claude Code will respond with a generated URL. Click the URL to open it in the browser. If you’re not already logged in to the Publisher Dashboard sandbox environment, you’ll be directed to log in. Once logged in, you’ll see a success screen in the browser.

5. In Claude Code, you should now see that you’re logged in and connected to the Appcharge MCP.

Claude Desktop

To connect the MCP server to Claude Desktop:

1. Log in to your Publisher Dashboard sandbox account.

2. Open Claude Desktop, and in the top navigation bar, go to Claude > Settings.

3. In the sidebar, go to Developer, and click Edit Config. Your file system opens with the Claude config file selected.

4. Drag the Claude Desktop config file into an AI coding assistant, then paste the following prompt:

   Read how to add an MCP server to Claude Desktop, then add the Appcharge MCP sandbox server to this config file.
   

   Claude Desktop requires MCP servers to be added in a specific format, so using an AI coding assistant helps make sure the configuration is added correctly.

5. Restart Claude Desktop.

6. Claude should recognize the new MCP server. Confirm that it appears as connected.

Other

To connect the MCP server to other MCP-compatible clients:

1. In your MCP-compatible client, add and save the Appcharge MCP server configuration. For more information on how to connect an MCP server, refer to your specific client documentation.

   {
     "appcharge-sandbox": {
       "url": "https://api-sandbox.appcharge.com/mcp",
       "timeout": 10000
     }
   }
   

2. Authenticate the MCP server by logging in to your Publisher Dashboard sandbox environment. Your client may provide a Connect button or prompt you to open an authorization URL in the browser, similar to the Cursor and Claude Code flows.

3. In your client, you should now see that you’re logged in and connected to the Appcharge MCP.

MCP tools

The Appcharge MCP server exposes the following tools.

Project tools

Use this tool to look up your Publisher Dashboard projects in the environment you connected to.

Tool name	Description	Use case
list_projects	Lists your Publisher Dashboard projects in the configured environment, including project ID, name, and type.	Find your project ID when configuring integrations or switching context between projects.

Documentation tools

Use these tools to interact with the Appcharge documentation.

Tool name	Description	Use case
list_docs	Lists all available documentation pages.	Discover available documentation pages without leaving your AI client.
get_doc	Fetches the full content of a specific article.	Read full documentation content for a specific topic or API reference page.
search_docs	Searches documentation by keyword.	Find documentation pages related to a keyword or integration topic.

Appcharge integration tools

Instead of configuring your developer settings manually in the Publisher Dashboard, use these tools to manage callback and webhook URLs in the environment you connected to.

Tool name	Description	Use case
get_webhooks_urls	Retrieves your current callback and webhook URL configuration from the Publisher Dashboard.	Check which integration URLs are configured, missing, or ready for onboarding validation.
update_webhooks_urls	Updates 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.
test_webhooks_urls	Validates your callback and webhook URL configuration in the Publisher Dashboard and reports any issues.	Check whether your integration URLs are reachable and correctly configured before onboarding.

Example prompts

After you connect the MCP server, try prompts such as:

Check which of my callback URLs are missing for my account

List the IDs for all my web store projects

Explain player authentication

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