MCP Connection Troubleshooting

← Back to Connect ProdPad to AI Tools with MCP
  • Availability
    • Plan: Modular v2 and Enterprise
  • Authentication
    • Method: OAuth 2.0 with the ProdPad client ID

When to use this article

The standard setup steps in Connect ProdPad to AI Tools with MCP let your AI tool identify itself to ProdPad automatically, so you don't need to enter a client ID.

If those steps don't work for you, you can connect using the ProdPad OAuth client ID instead. This can help if:

  • You're using an older version of your AI tool
  • Your organisation's settings stop the AI tool from using its own published identity
  • The sign-in fails with an error about client registration

The ProdPad OAuth client ID is:

a0765d4d5f424c55ba8dc037bc2d6342

Before you try these steps

Many connection problems are fixed by updating your AI tool and connecting again. Before using a client ID, try:

  • Updating your AI tool to the latest version
  • Removing the ProdPad connection and adding it again (see Starting the sign-in again)
  • Signing out of ProdPad in your browser, or using a private/incognito window for the sign-in
  • Confirming your ProdPad account is on an MV2 or Enterprise plan

Claude on the web or the desktop app

  1. Go to claude.ai/customize/connectors (or Customize > Connectors in the desktop app). If you've already added ProdPad, remove it first.
  2. Click Add, then Add custom connector.
  3. Add ProdPad for the name, and add https://api.prodpad.com/mcp for the Remote MCP server URL.
  4. Instead of using Claude's published identity, open Advanced settings and add a0765d4d5f424c55ba8dc037bc2d6342 for the OAuth Client ID.
  5. Click Add to finish.
  6. Click Connect to authenticate with ProdPad (if you don't see the Connect button, refresh the tools list from the overflow menu and it should appear).
  7. Click Accept & continue to complete the authentication process.

Claude Code (CLI)

If you've already added ProdPad, remove it first:

claude mcp remove prodpad

Then run the following command in your terminal:

claude mcp add --transport http --client-id a0765d4d5f424c55ba8dc037bc2d6342 prodpad https://api.prodpad.com/mcp

Then type /mcp in Claude Code and follow the authentication prompt to connect your ProdPad account. You may need to exit your current session for the /mcp list to refresh.


ChatGPT

Please note that OpenAI has been updating UI frequently after unifying with Codex, these instructions may not exactly reflect what you see, if you need help - let us know!

  1. Open ChatGPT. If you've already added ProdPad, remove it first.
  2. Navigate to Plugins in Settings
  3. Add a new Plugin
  4. Enter a name for the ProdPad MCP
  5. In the Connection field, enter the ProdPad server url: https://api.prodpad.com/mcp
  6. Make sure OAuth is selected for authentication and click on Advanced OAuth settings
  7. In the OAuth Client ID field, enter a0765d4d5f424c55ba8dc037bc2d6342
  8. Click the checkbox "I understand and want to continue..." and click Create
  9. Complete the OAuth authorization flow to Sign in with ProdPad MCP
  10. Return to ChatGPT - you should now be able to select ProdPad from the + menu.

GitHub Copilot CLI

GitHub Copilot CLI doesn't currently support connecting with a client ID. If the standard setup doesn't work, try the following:

  1. Check your Node.js version with node --version. You need Node.js 22 or later.
  2. Update Copilot CLI:
    npm install -g @github/copilot
    	
  3. Check your Copilot CLI version with copilot --version. You need version 1.0.83 or later.
  4. Remove the ProdPad connection and add it again (see Starting the sign-in again).

If it still doesn't connect, you can use an API key instead of OAuth, or contact us for help.


Starting the sign-in again

If a previous attempt failed, your AI tool may have saved details from that attempt. Clear them before trying again.

Claude on the web or the desktop app

Remove the ProdPad connector from Customize > Connectors, then add it again.

Claude Code

Type /mcp, select prodpad and choose to clear authentication. Or remove the server with claude mcp remove prodpad and add it again.

ChatGPT

Remove the ProdPad plugin from Settings, then add it again.

GitHub Copilot CLI

  1. Exit any running Copilot CLI session.
  2. Remove the server:
    copilot mcp remove prodpad
    	
  3. Delete the saved sign-in details for ProdPad from the ~/.copilot/mcp-oauth-config/ folder. To find the right file, run:
    grep -l "prodpad" ~/.copilot/mcp-oauth-config/*
    	
  4. Add the server again:
    copilot mcp add --transport http prodpad https://api.prodpad.com/mcp
    	
  5. Start Copilot CLI, type /mcp, select prodpad and authenticate.

For any tool, signing out of ProdPad in your browser, or using a private/incognito window for the sign-in, also makes sure you start with a fresh ProdPad session.


Common error messages

"Authorization server does not support dynamic client registration"

Your AI tool is too old to identify itself to ProdPad automatically. Update it to the latest version and try again. For Claude Code you need version 2.1.81 or later, and for GitHub Copilot CLI version 1.0.83 or later. If you can't update, follow the client ID steps for your tool above.

"Invalid redirect URI" or "Callback URL mismatch"

The sign-in returned to a different address than expected. Remove the connection, clear any saved sign-in details (see Starting the sign-in again) and try again. If the error continues, contact us and let us know which AI tool and version you're using.

"No platform package found" (GitHub Copilot CLI)

Your Node.js version is too old or is running in the wrong mode, for example an Intel build of Node.js on an Apple Silicon Mac. Install Node.js 22 or later and reinstall Copilot CLI.

ProdPad shows as not authenticated or the session has expired

Reconnect ProdPad from your AI tool's connector or MCP settings and complete the sign-in again.

Still stuck? Contact us and let us know which AI tool you're using, its version, and the exact error message you see.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us