HasData TikTok

TikTok MCP Server

A hosted TikTok MCP server that gives Claude, Cursor, Windsurf and any other MCP client four read-only TikTok tools. Look up a public profile, walk an account's videos, read the comments on a video, and search TikTok for videos or creators, all as structured JSON, with no TikTok developer account and no OAuth.

It reads public data that a signed-out visitor can see. It does not sign in, post, or act as an account.

1,000 free credits every month, no card required, which is 100 TikTok calls.

https://mcp.hasdata.com/mcp?apis=tiktok

[Glama score] [tool contract] [MCP] [Tools]

• Prompts and resources [npm] [PyPI] [License]

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• Tool selection
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

What you need

An MCP client and a HasData API key from the dashboard, free to create. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no TikTok developer account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/tiktok-mcp on npm and hasdata-tiktok-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

claude mcp add --transport http tiktok "https://mcp.hasdata.com/mcp?apis=tiktok" \  --header "x-api-key: HASDATA_API_KEY"

{  "mcpServers": {    "tiktok": {      "command": "npx",      "args": ["-y", "@hasdata/tiktok-mcp"],      "env": { "HASDATA_API_KEY": "YOUR_KEY" }    }  }}

{  "mcpServers": {    "tiktok": {      "command": "uvx",      "args": ["hasdata-tiktok-mcp"],      "env": { "HASDATA_API_KEY": "YOUR_KEY" }    }  }}

{  "mcpServers": {    "tiktok": {      "url": "https://mcp.hasdata.com/mcp?apis=tiktok",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

{  "mcpServers": {    "tiktok": {      "serverUrl": "https://mcp.hasdata.com/mcp?apis=tiktok",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

{  "mcpServers": {    "tiktok": {      "url": "https://mcp.hasdata.com/mcp?apis=tiktok",      "type": "streamableHttp",      "headers": { "x-api-key": "HASDATA_API_KEY" },      "disabled": false    }  }}

{  "servers": {    "tiktok": {      "type": "http",      "url": "https://mcp.hasdata.com/mcp?apis=tiktok",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

[mcp_servers.tiktok]url = "https://mcp.hasdata.com/mcp?apis=tiktok"
[mcp_servers.tiktok.headers]"x-api-key" = "HASDATA_API_KEY"

{  "mcpServers": {    "tiktok": {      "httpUrl": "https://mcp.hasdata.com/mcp?apis=tiktok",      "headers": { "x-api-key": "HASDATA_API_KEY" }    }  }}

Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because in MCP the model decides how many calls to make and every successful call costs 10 credits.

Take @mrbeast. Pull the profile, then walk the first two pages of videos and give me the median play count across them.

Three calls, 30 credits. The profile is one call, and each page of videos is another.

Search TikTok for creators around "cold brew coffee" and rank the top ten by followers, each with their bio.

One call, 10 credits. A user search already carries follower count and bio, so no per-profile follow-up is needed.

Here is a video URL. Read its top comments and tell me the overall sentiment and the three most-liked replies.

One call, 10 credits. The numeric id in the URL is all the comments tool needs.

Take that same video, then expand the replies under its most-liked comment.

Two calls, 20 credits. Top-level comments first, then a second call with that comment's id for its replies.

Search "asmr" videos, then pull the author profile of the three with the highest play counts.

Four calls, 40 credits. One search, then one profile each. Every author in a search result carries a link straight to its profile endpoint, so the agent never has to guess a handle.

Paging costs a call each time. A creator audit that reads a profile then walks five pages of videos is six calls and 60 credits. The free tier goes further on narrow questions than on open-ended crawls.

Tools

Four tools, all read-only. Samples below are trimmed from real calls, and the numbers in them move as TikTok updates. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.

The samples are the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.

Handles, video ids and comment ids chain together. A profile links to its posts, every post carries its own video id for the comments tool, and every author in comments and search results carries a hasdataLink to its profile and a hasdataPostsLink to its videos. An agent walks from a keyword to a creator to a video to its comments without ever constructing a URL.

Get TikTok profile

hasdata_tiktok_profile_getTikTokProfile

One public account by handle.

Returns username, nickname, biography, bioLink, verified, language, createTime, the avatar URLs, and the followers, follows, likes, videos and friends counts as integers. The counts are already parsed, so followers > 1000000 compares numbers, not display strings.

A handle that does not exist still comes back with requestMetadata.status set to ok, the profile object simply absent. Check that the object is there before reading username or any other field, or an agent doing profile.username throws on nothing.

{  "username": "mrbeast",  "nickname": "MrBeast",  "verified": true,  "biography": "Checkout My New Book!👇",  "bioLink": "http://themostdangerousgames.com",  "createTime": "2018-10-20T19:26:16.000Z",  "followers": 138387571,  "follows": 354,  "likes": 1427086888,  "videos": 466,  "friends": 285}

Get TikTok posts

hasdata_tiktok_posts_getTikTokPosts

A page of an account's videos by handle, newest first.

One call returns about thirty videos plus pagination, which carries hasMore and the nextPageToken you feed back to walk the account history one page at a time. Each video carries id, description, url, duration, the cover and playable video URLs, music, and the likes, comments, shares, plays, collects and reposts counts as integers.

hashtags and mentions are present only on videos that carry them, and how often that happens follows the account rather than the endpoint. Sampled feeds ranged from no tagged posts at all to every post tagged. Test for the key before you read it, and read an absent array as an account that does not tag.

{  "id": "7677375185028271391",  "description": "would you take the car or nah?",  "url": "https://www.tiktok.com/@mrbeast/video/7677375185028271391",  "createTime": "2026-08-23T23:36:59.000Z",  "duration": 41,  "likes": 129500,  "comments": 6670,  "shares": 2033,  "plays": 1100000,  "collects": 4986,  "music": { "title": "original sound", "authorName": "MrBeast", "original": true }}

Get TikTok comments

hasdata_tiktok_comments_getTikTokComments

The comments on a public video, or the replies under one comment.

Each comment carries text, likes, createTime, replyCount and an author, and every author carries a hasdataLink to its profile and a hasdataPostsLink to its videos. pagination.total reports the video's whole comment count, so you know the depth before you page. A comment with a non-zero replyCount has replies you reach by calling again with its id as commentId.

{  "id": "7677377150003053325",  "text": "How could someone turn down a car",  "createTime": "2026-08-23T23:45:06.000Z",  "likes": 3802,  "replyCount": 22,  "author": {    "username": "hohce.verggr",    "nickname": "Sasori",    "hasdataLink": "https://api.hasdata.com/scrape/tiktok/profile?handle=hohce.verggr",    "hasdataPostsLink": "https://api.hasdata.com/scrape/tiktok/posts?handle=hohce.verggr"  }}

Search TikTok

hasdata_tiktok_search_getTikTokSearch

A keyword search over videos or creators.

With type: video the response holds videos in the same shape the posts tool returns, each with its author. With type: user it holds creators, each with username, nickname, signature (the bio), avatarUrl, followers, and the same hasdataLink and hasdataPostsLink to chain into a profile or its videos. A verified flag is present on accounts that carry one.

{  "username": "la.mooncoldbrew",  "nickname": "lamoon cold brew coffee",  "signature": "อยากได้สูตรชงเมนูไหน Comment ไว้เลยน้า",  "followers": 48000,  "hasdataLink": "https://api.hasdata.com/scrape/tiktok/profile?handle=la.mooncoldbrew",  "hasdataPostsLink": "https://api.hasdata.com/scrape/tiktok/posts?handle=la.mooncoldbrew"}

Prompts and resources

The server ships 2 prompts, ready-made workflows a client can offer instead of making the user compose a tool call.

Alongside them the server exposes one resource, the accepted values of the single parameter that takes a fixed list. Reading it is cheaper than learning the vocabulary from a rejected call, and it costs no credits.

Its URI is hasdata://tiktok/type.

Both lists are served without an API key, so a client can read them before a user has signed up.

Errors and failure paths

Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with isError set to true and the reason as text. The agent reads a message where you might expect a status line.

A wrong key surfaces as tool output, not as a failed connection. tools/list accepts any non-empty key and returns all four tools, so the client completes its handshake and shows green. The first tool call then comes back with isError: true and the text HasData API error: 401 Unauthorized. Watch for that string, because nothing earlier in the flow reports the problem.

A missing key is the one real HTTP error. Authorization runs before any tool, and the connection itself fails with 401. CORS headers are present, and a browser client reads the status and not an opaque network failure.

An argument that breaks a tool's schema is rejected before it becomes a scrape. The server answers with isError: true and the text MCP error -32602: Input validation error, naming the offending field. Nothing is fetched and nothing is charged.

A call that succeeds and finds nothing is the case that trips people up. A handle that does not exist comes back as an ordinary result with requestMetadata.status set to ok and the data key simply missing. Nothing in the body says the result was empty. Test for the field you need, not for an error.

An identifier the platform rejects returns 400 with requestMetadata.status set to error.

Results that carry data also carry a requestMetadata.id worth quoting in support.

Pricing, free tier and limits

Every TikTok tool costs 10 credits per successful call. Response size does not change the price. A full page of videos costs the same as a profile with one field.

The free tier is 1,000 credits every month with no card, which is 100 TikTok calls. It renews with the billing cycle, so a low-volume agent runs on the free tier indefinitely.

Paid plans start at $59 a month for 200,000 credits, which is 20,000 calls. The unit price falls with volume, from $2.95 per 1,000 calls on the entry plan to $1.19 on Basic and $0.83 across the Growth tiers. Current figures live on the pricing page.

Your plan also sets concurrency. The free tier allows 5 requests at a time, Startup 5, Basic 15, and the Growth tiers run from 50 to 500. Handle the overflow case defensively in anything unattended, because an agent that fans out will reach the ceiling before you do.

A request that comes back non-200 is not billed. A successful call that finds nothing is still a call.

Tool selection

The apis query parameter decides which tools your agent sees. Fewer tools means less context spent on tool definitions, and fewer chances for the model to reach for the wrong one.

?apis=tiktok                     the four tools in this repo?apis=tiktok,instagram           a social bundle?apis=tiktok,google_serp         add Google search

The parameter takes provider names like tiktok and individual API names like tiktok_search. Misspelled names are ignored. If every name is wrong the request fails with 400, and the body lists both what it did not recognise and every valid value. Drop the parameter and the same endpoint exposes all 57 HasData tools.

How it compares

TikTok's own developer program does not cover general reading of public content. The Research API is gated behind an application and open to approved academic and nonprofit researchers in a limited set of regions. The Display API returns only the content of the account that signs in over OAuth. Neither fits an agent that needs to read an arbitrary public profile, its videos, or a video's comments.

Most other TikTok MCP servers wrap a single unofficial endpoint. This one covers the four reads an agent actually chains, profile to posts to comments, plus search, so a whole research pass runs against one server.

What this server does not do. No posting, no direct messages, no follower-only or private content, no analytics for accounts you do not own. It reads what a signed-out visitor can see.

FAQ

Is there an official TikTok MCP server?

TikTok does not publish one. Every option is built by somebody else. This one is maintained by HasData and reads public pages, which is why it needs no TikTok developer account.

What is a TikTok MCP server?

A server that exposes TikTok data as tools an AI client can call. The client sends a tool call over the Model Context Protocol, the server fetches the data and returns structured JSON, and the model works with the result and never sees a page of HTML. This one exposes four tools and runs remotely. The client connects to a URL and starts no local process.

Do I need a TikTok API key or a developer account?

No. The only credential is your HasData key. There is no developer application to file and no OAuth consent screen, because the tools read public TikTok pages and not the TikTok developer APIs.

Do I need to host or run anything?

No. This is a remote MCP server on streamable HTTP. Nothing to install, no container to keep warm, no process to restart.

Is the data live or cached?

Live. Each call fetches at request time and carries its own requestMetadata.id. Counters like plays and likes track the page, so they move as the page moves.

Can I read a private account?

No. The tools return what a signed-out visitor sees. A private account's videos are not public, so they are not in any response.

Can I read comment replies, not just top-level comments?

Yes. Call the comments tool with a comment's id as commentId and it returns that comment's replies. A comment's replyCount tells you whether there are any.

Can I use this together with other HasData APIs?

Yes. The apis parameter takes a list, and ?apis=tiktok,instagram gives your agent the four TikTok tools plus Instagram. Drop the parameter and you get everything.

Compliance and personal data

HasData accesses publicly available data only. A platform's terms may restrict automated access, and you are responsible for your own compliance. Where the data you collect includes personal information, make sure you have a lawful basis for it under GDPR, CCPA or the equivalent rules in your jurisdiction.

HasData links

Development

This repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.

The tests in test/ assert the tool contract, the part that can break without a commit here. They check that ?apis=tiktok returns exactly four tools, that every tool still declares its required parameter, that no name changed, and that the key in use is actually accepted. That last check calls a tool for real and costs 10 credits, which is the price of a canary that can fail for the right reason.

# macOS and LinuxHASDATA_API_KEY=your_key_here npm test
# Windows PowerShell$env:HASDATA_API_KEY="your_key_here"; npm test

The same suite runs in CI on every push and once a week on a schedule, because the upstream tool list can change without anyone touching this repository. A failure means the tool list moved, the key stopped working, or the endpoint was unreachable, and the assertion message says which.

Contributing

Corrections to the tool tables and the response samples are the most useful contribution, because those are the parts that drift. Include the call you made and the response you got. Pull requests from forks run the suite without a key, and the live checks skip instead of going red.

License

MIT. See LICENSE.