Shops, orders, products, fulfillment, logistics, finance and returns — exposed over one authenticated endpoint. The Partner Center app secret and every seller token stay on the server; clients only hold a per-user bearer token.
https://tiktok-remote-mcp.nutrifarm.id/mcp
One POST /mcp endpoint, JSON responses, no session state to keep alive between calls.
readonly sees read tools, readwrite can mutate, admin adds shop management.
Dynamic client registration and PKCE, so ChatGPT and Claude.ai connectors link without pasting a token.
Three ways in — pick the one that matches your client.
An admin creates it once with the CLI (npm run cli -- user add) or the admin TUI (npm run admin).
The token is shown a single time; only its SHA-256 hash is stored.
npm run cli -- user add alice readwrite
Adds the server with a static header, no OAuth round trip.
claude mcp add --transport http tiktok-shop https://tiktok-remote-mcp.nutrifarm.id/mcp \ --header "Authorization: Bearer <user-token>"
Same server, configured with a static header.
{
"mcpServers": {
"tiktok-shop": {
"url": "https://tiktok-remote-mcp.nutrifarm.id/mcp",
"headers": { "Authorization": "Bearer <user-token>" }
}
}
}
These clients cannot send a custom header. Add https://tiktok-remote-mcp.nutrifarm.id/mcp as a custom
connector and approve the OAuth prompt with your existing token — discovery is served from
/.well-known/oauth-authorization-server.
Everything except the landing page needs a bearer token.
POST https://tiktok-remote-mcp.nutrifarm.id/mcp # MCP tools (auth required) GET https://tiktok-remote-mcp.nutrifarm.id/healthz # liveness probe (public) GET https://tiktok-remote-mcp.nutrifarm.id/README.md # machine-readable docs