MCP server
Use the API as tools in Claude, Cursor, VS Code and other agents. Same key, same prices.
The MCP server exposes each endpoint as a tool. Each tool call is one HTTP call to https://scraper.riken.me with your own key, and returns the API's JSON answer unchanged. Prices are the same as the API's, and errors are free.
Tools
| tool | endpoint | cost |
|---|---|---|
tiktok_profile | GET /v1/tiktok/profile | 1 credit |
tiktok_profile_videos | GET /v3/tiktok/profile/videos (page 1 in beta) | 1 credit |
tiktok_search_keyword | GET /v1/tiktok/search/keyword | 1 credit per page |
tiktok_user_followers | GET /v1/tiktok/user/followers | 1 credit per page, when it opens |
tiktok_user_audience | GET /v1/tiktok/user/audience | 20 credits, when it opens |
Arguments are the endpoint's parameters: handle or user_id, and query and cursor for search. Every tool also takes an optional idempotency_key.
Each result has two text blocks: the API's JSON body, byte for byte, and one line of HTTP facts such as http_status=200 search_region=US request_id=.... A non-2xx answer is a tool error (isError: true) carrying the API's error body, so the model sees the error code. The server never retries on its own.
Connect
Remote endpoint not live yet
The hosted endpoint https://scraper.riken.me/mcp is planned, with your API key in a header. Until it opens, run the server locally over stdio (the second tab of each client).
Remote:
claude mcp add --transport http riken-scraper https://scraper.riken.me/mcp \
--header "x-api-key: $RIKEN_API_KEY"Local (stdio):
claude mcp add riken-scraper \
-e CREATOR_API_BASE_URL=https://scraper.riken.me \
-e CREATOR_API_KEY=$RIKEN_API_KEY \
-- /absolute/path/to/mcpserverThen run /mcp in Claude Code to check it is connected. If long calls are cut off, raise MCP_TOOL_TIMEOUT (milliseconds).
Configuration of the local server
| flag | environment | meaning |
|---|---|---|
-base-url | CREATOR_API_BASE_URL | the API base URL, https://scraper.riken.me |
-api-key | CREATOR_API_KEY | your API key (stdio only). Prefer the environment. |
-http ADDR | serve streamable HTTP at http://ADDR/mcp instead of stdio |
In HTTP mode every request must carry the caller's own key as x-api-key or Authorization: Bearer. The server's own key is never used, so one caller can never spend another's credits.
Timeouts
The API holds a request up to 180 seconds. The server waits 200 seconds for an answer (6 minutes for audience). Some clients give up on a tool call sooner, so raise their tool timeout if long calls are cut off.