Troubleshooting

Configuration not loading:

• Verify the JSON syntax is correct (use a JSON validator).
• Ensure the file is saved in the correct location.
• Check file permissions allow reading.

AI assistant not accessing PandaDoc data:

• Confirm you restarted your AI development tool after configuration.
• Verify the MCP server URL matches the region your PandaDoc account is hosted in:
  • Global: https://mcp.pandadoc.com/v1/mcp
  • European: https://mcp.pandadoc.eu/v1/mcp
• Check if your tool supports MCP and has it enabled.

Authentication fails or your account isn't recognized:

• Check which region you're in: if you sign in at app.pandadoc.eu, your account is in the European region and must connect to https://mcp.pandadoc.eu/v1/mcp. Accounts on app.pandadoc.com use https://mcp.pandadoc.com/v1/mcp.
• A region mismatch is the most common cause of failed authentication. Accounts exist separately in each region, so the global server can't authenticate a European account, and vice versa.
• In Claude Desktop, don't install the PandaDoc connector from the Claude connector directory if your account is in the European region. That listing connects to the global server only — there is no PandaDoc connector in the directory for the European region. Add PandaDoc as a custom connector with the https://mcp.pandadoc.eu/v1/mcp URL instead.
• To fix a wrong URL, remove the PandaDoc server or connector from your client, add it again with the correct regional URL, then authenticate again.

Connected, but documents or templates are missing:

• Each regional server returns only the documents and templates stored in its own region. If results are empty or incomplete, confirm you're connected to the region that holds your data.
• Confirm you authorized the PandaDoc account (and workspace) you expected during authentication. If you authorized the wrong one, disconnect the server in your client and authenticate again.

For setup steps per client and the full region reference, see Getting Started with MCP.