Can AI agents automate PandaDoc?

PandaDoc is automatable today through a first-party remote MCP server and a REST API. MCP is at https://mcp.pandadoc.com/v1/mcp globally and https://mcp.pandadoc.eu/v1/mcp for accounts that sign in at app.pandadoc.eu. Auth is OAuth. Region mismatch fails authentication, and each host returns only that region's documents. The Claude directory listing points at the global host only. The REST API at https://api.pandadoc.com follows resource URLs and standard HTTP methods. OAuth 2.0 Bearer is recommended; API-Key is documented as a legacy workspace key. Production API keys require the Enterprise plan and vendor activation. Sandbox keys exist for testing and limit sending to the account domain. Official SDKs are listed for Python, Node, Java, and PHP. Webhook subscriptions notify document and template changes, with a 300-subscription cap per workspace. This record excludes Docusign and Oneflow. The marketing homepage returned HTTP 429 in this pass; identity is taken from developer docs. Connector catalogs and a product CLI were not established. Computer-use viability is unassessed. MCP scores 8 and is the best path because it is the opened self-serve agent surface and does not require the Enterprise production-key activation documented for REST.

Best path today: mcp · Overall automatability: 8/10