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.
Discover a capability, read its contract, then choose the next request. Connect with local OAuth, stdio or a separate HTTP service.
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.
These key-based modes remain separate from OAuth. Store credentials in your local client's private configuration.
Run node scripts/mcp-server.mjs in a complete copy of the project. Set GUANLIU_MCP_PORT to the website's port.
Use the configuration form below. It generates local JSON and never reads files or starts a process.
npm run mcp:http -- --port 4322 --upstream-port 4321
Connect a native local client to http://127.0.0.1:4322/mcp. Key-based modes require X-Guanliu-Mode and a matching Bearer key. Protocol: 2025-06-18, JSON responses, no SSE or automatic retry.
Enter the absolute project path to prepare a configuration.
No configuration prepared.
4 / 7 / 3demo: find, describe, call, read_more. simulated adds quote, account and run. live offers find, describe and account only; it reads saved records and cannot execute supplier requests.Public capability coverage describes contracts, not live availability.