One endpoint. A clear starting point.
https://datanavoapi.com/api/mcpLocal OAuth grants access to the catalog and fixed fixtures. It does not use a customer key or consume TEST credit.
Sign in, review permissions, connect tools. Each application receives its own revocable authorization.
https://datanavoapi.com/api/mcpLocal OAuth grants access to the catalog and fixed fixtures. It does not use a customer key or consume TEST credit.
mcp:readRead the catalogmcp:demoRun fixed fixturesOAuth access to account records, customer billing and supplier execution is not enabled. Existing key-based connections remain separate.
Start with the built-in inspector, or register exact callback URLs for your own local client.
PKCE protects the code exchange. Only approved tools become available.
Manually refresh short-lived access, or revoke it from your connections page.
Reads public metadata only. It does not authorize an app or execute tools.
Register your application name and exact HTTP loopback callback URL in Agent connections. The built-in inspector is preregistered. The consent page shows requested permissions and the destination before approval or denial.
Codes are short-lived and single-use. Access tokens last 10 minutes. Refresh tokens rotate; reuse revokes their family. Revoke clients or grants from the connections page.
The browser inspector stores tokens only in page memory; reconnect after reload. Reinitialize after session expiry or server restart. Tools are never retried automatically. Return to connections to start again after denial.
This release does not deploy a public authorization server or claim cloud-client compatibility. A stable HTTPS domain and deployment, registered client callbacks, production storage and rate limits are still required. Alipay sandbox remains deferred.