Generic MCP

Configure DigitalPublic in another agent

Streamable HTTP and OAuth 2.1 with PKCE are recommended, with structured contracts and actionable errors.

01

Public discovery

mcp.json
{"mcpServers":{"digitalpublic-commercial":{"url":"https://platform.digitalpublic.com/api/mcp-commercial"}}}
02

Operational product

The client should follow the OAuth challenge advertised by the server. Never paste tokens into a conversation.

mcp.json
{"mcpServers":{"digitalpublic":{"url":"https://platform.digitalpublic.com/api/mcp"}}}
03

Compatible approval

  • OAuth approve is independent from read and write.
  • Use MCP elicitation when the client negotiates it.
  • As a second option, use the decision tool with native human confirmation.
  • If the client supports neither MCP Apps, permissions, nor elicitation, DigitalPublic returns the safe portal link without executing anything.
04

Advanced compatibility

The owner or an administrator can create a project-scoped credential in the portal for clients without OAuth. They can choose read only or read and write when the plan and connector support it. dpk_, dpa_, and mcp-remote remain available but are not the primary journey.

Machine-readable evidence

The same facts are available through API and MCP.

OpenAPI