AUTHORIZE A CONNECTION

Let every connection begin with consent.

Sign in, review permissions, connect tools. Each application receives its own revocable authorization.

One endpoint. A clear starting point.

https://datanavoapi.com/api/mcp

Local OAuth grants access to the catalog and fixed fixtures. It does not use a customer key or consume TEST credit.

YOU CHOOSE THE SCOPE
mcp:readRead the catalog
find · describe
mcp:demoRun fixed fixtures
call · read_more

OAuth access to account records, customer billing and supplier execution is not enabled. Existing key-based connections remain separate.

  1. 01Choose a client and permissions

    Start with the built-in inspector, or register exact callback URLs for your own local client.

  2. 02Approve, then run a fixture

    PKCE protects the code exchange. Only approved tools become available.

  3. 03Expire, refresh or revoke

    Manually refresh short-lived access, or revoke it from your connections page.

Check local discovery

Reads public metadata only. It does not authorize an app or execute tools.

No domain purchase is needed now. Cloud clients require a stable HTTPS deployment and cannot reach this loopback address.

BEFORE YOU CONNECT

An authorization flow you can inspect.

Registration and consent

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.

Credential lifecycle

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.

Disconnect and recovery

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.

Beyond loopback

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.