DataNavoAPI / DOCS

MCP protocol access

MCP protocol access. Follow concrete contracts, examples and reviewable steps using Douyin, Bilibili, Kuaishou, Telegram.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

MCP protocol access

Use local stdio or the independent Streamable HTTP service. Its loopback URL is not directly reachable by a cloud client.

Anonymous mode provides find, describe, call and read_more; customer simulated mode adds quote, account and run, for seven tools. Creating a run budget requires explicit confirm; reading an existing budget is read-only.

Specify inputs, mode and idempotency explicitly; read the original receipt when the outcome is unknown.

sh
npm run mcp
# Separate local HTTP transport:
npm run mcp:http -- --port 4322 --upstream-port 4321
02

Local exercise boundaries

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

TEST credits are not money. Use an isolated account to verify success, failure, timeout, replay and key revocation.

TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗