threads-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADS_USER_ID | Yes | ID tài khoản Threads | |
| THREADS_ACCESS_TOKEN | Yes | Access Token (quyền threads_content_publish) | |
| THREADS_GRAPH_VERSION | No | Mặc định v1.0 | 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Lay thong tin ho so Threads (username, ten, tieu su). |
| post_textC | Dang bai text len Threads. |
| post_imageC | Dang bai kem 1 anh len Threads tu URL anh cong khai. |
| post_videoC | Dang bai kem video len Threads tu URL video cong khai. |
| post_carouselC | Dang carousel (nhieu anh/video) len Threads. |
| list_threadsC | Lay danh sach bai da dang tren Threads. |
| get_threadC | Lay chi tiet mot bai theo thread_id. |
| get_repliesD | Lay cac reply cua mot bai. |
| replyC | Tra loi (reply) vao mot bai Threads. |
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 9 tools
Each tool targets a distinct action: posting types (text, image, video, carousel), retrieval (list, get), and interaction (reply, get_replies, get_profile). No overlap in functionality.
All tools follow a clear verb_noun pattern (e.g., post_text, get_thread, list_threads) with consistent snake_case. No deviations or mixed conventions.
9 tools cover key Threads operations (posting multiple formats, reading, replying) without bloat or deficiency. Well-scoped for a social media API.
Core workflows are complete: create (text, image, video, carousel), read (list, get, get_replies, profile), and reply. Minor gaps: no delete or update operations, but these are not essential for basic usage.