Threads API MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADS_USER_ID | No | User ID (Optional, default: "me") | me |
| THREADS_ACCESS_TOKEN | Yes | Meta Threads User Access Token (Required) | |
| THREADS_API_BASE_URL | No | API Base URL (Optional) | https://graph.threads.net/v1.0 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profile_infoA | Fetch the authenticated Threads user's profile information. Returns: JSON string containing user id, username, bio, avatar URL, and profile link. |
| list_recent_postsA | Fetch recent posts from the authenticated user's Threads account. Args: limit: Number of posts to retrieve (1 to 100, default 25). after: Pagination cursor for fetching subsequent posts page. before: Pagination cursor for fetching previous posts page. Returns: JSON string with list of posts (id, text, media_type, timestamp, permalink) and pagination cursors. |
| get_post_detailsA | Fetch detailed metadata for a single Threads post. Args: media_id: Unique Threads post/media ID. Returns: JSON string with post content, author username, timestamp, permalink, and media info. |
| get_post_analyticsA | Fetch engagement analytics (views, likes, replies, reposts, quotes) for a specific post. Args: media_id: Unique Threads post/media ID. Returns: JSON string containing numeric metrics (views, likes, replies, reposts, quotes) and raw data. |
| get_account_analyticsA | Fetch aggregated engagement metrics for the account over a specified time window. Args: metric_types: List of metrics (e.g. ["views", "likes", "reposts", "quotes", "followers_count"]). days_back: Number of past days to query (default: 7). Returns: JSON string containing aggregated metric totals. |
| fetch_post_repliesA | Fetch replies and comments attached to a specific Threads post. Args: media_id: Unique Threads post/media ID. reverse_sort: If True, returns newest replies first. If False, returns chronological order. limit: Max replies to fetch (default 50). after: Pagination cursor for next page of replies. Returns: JSON string containing list of replies (id, text, timestamp, username, permalink) and cursors. |
| export_postsA | Export recent posts formatted as a clean flat JSON list for archiving, analysis, or vector embeddings. Args: limit: Number of posts to export (default 50, max 100). Returns: JSON string containing flat simplified post items with ID, text, timestamp, and URL. |
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 7 tools
Most tools map to a distinct resource and action, such as profile, post list, post details, post analytics, account analytics, replies, and export. The only real overlap risk is between list_recent_posts and export_posts, but their output purpose and shape are different enough to avoid serious misselection.
Tool names generally follow a clear verb_noun pattern, e.g. get_profile_info, list_recent_posts, get_post_details. The main inconsistency is using get, list, fetch, and export as interchangeable retrieval verbs, but no convention mixing like camelCase or inconsistent singular/plural occurs.
Seven tools is well-scoped for a Threads read-and-analytics server. Each tool covers a coherent slice of functionality without unnecessary bloat or padding.
The tool set covers profile retrieval, recent posts, post details, replies, per-post analytics, account analytics, and data export, so common read-only workflows are complete. Write/publish and search operations are absent, but they appear outside this server's apparent scope.