Threads Profile and Posts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a tool call requires one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_threads_profilesA | Read public Threads profiles the way a logged out visitor sees them. Returns one row per profile with username, name, verified mark, follower count, bio, bio links, and profile photo, plus one row per post the profile page shows (the newest threads and the author's continuation posts) with text, date, likes, replies, reposts, quotes, and media links. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of mistaking it for another. Its purpose (reading public Threads profiles and their posts) is stated explicitly and unambiguously.
The single name get_threads_profiles follows a clear verb_noun snake_case convention. There are no competing naming styles to create inconsistency.
A single tool is too thin for a domain that includes profiles, individual posts, and post retrieval. Fetching a profile and enumerating its posts are bundled into one monolithic call with no finer-grained operations.
Only a logged-out profile read is exposed; there is no way to fetch a specific post by ID/URL, search profiles or content, or paginate beyond what the profile page displays. Agents needing post-level or query-level access will hit a dead end.