threads-mcp
This MCP server lets you publish and manage Threads content through the Meta Threads API.
Get Threads profile details (username, name, bio).
Post text-only threads.
Post image threads from public image URLs, with optional caption.
Post video threads from public video URLs, with optional caption.
Post carousel threads with multiple image/video items.
List published threads, with configurable limit (default 10).
Get details for a specific thread by thread_id.
Get replies to a thread.
Reply to a thread.
Support multi-account use via optional per-call threads_user_id and access_token; otherwise use environment defaults.
Run over STDIO (npx/local) or HTTP remote with bearer-token auth.
Allows posting and managing Threads content, including text, images, videos, carousels, and interactions such as replying and viewing threads via the Meta Threads API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@threads-mcp post a text thread saying 'Hello from Threads!'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Threads MCP Server
MCP đăng & quản lý nội dung Threads qua Meta Threads API. Chạy được STDIO (npx từ GitHub, dùng local) hoặc HTTP (deploy remote cho Evose). Ai cũng dùng được — chỉ điền biến môi trường, không sửa code.
9 tools: get_profile, post_text, post_image, post_video, post_carousel, list_threads, get_thread, get_replies, reply.
Đăng theo quy trình container (tạo → chờ xử lý nếu có video → publish).
Mọi tool nhận thêm hai tham số tuỳ chọn threads_user_id và access_token, nên một bản chạy phục vụ được nhiều tài khoản. Không truyền thì server dùng biến môi trường làm giá trị mặc định.
Truyền threads_user_id thì phải truyền cả access_token, và ngược lại. Truyền nửa cặp thì server báo thiếu cấu hình chứ không lặng lẽ dùng credential mặc định. Một ô để trống từng làm bài của tài khoản này đăng lên tài khoản khác mà vẫn báo thành công.
Mọi tham số id chỉ nhận chữ số, chữ cái và dấu gạch dưới, tối đa 64 ký tự. Id chứa /, ? hay & bị từ chối, vì nó đổi được endpoint Graph API.
Biến môi trường
Biến | Bắt buộc | Mô tả |
THREADS_USER_ID | ✅ | ID tài khoản Threads |
THREADS_ACCESS_TOKEN | ✅ | Access Token (quyền threads_content_publish) |
THREADS_GRAPH_VERSION | ❌ | Mặc định v1.0 |
MCP_TRANSPORT | ❌ |
|
MCP_AUTH_TOKEN | Bắt buộc khi | Secret dùng cho header |
HOST | ❌ | Địa chỉ bind khi chạy HTTP, mặc định |
PORT | ❌ | Cổng lắng nghe khi chạy HTTP, mặc định |
MCP_PUBLIC_HOST | ❌ | Hostname công khai (qua reverse proxy) để chặn DNS rebinding |
Hai biến bắt buộc ở trên chỉ bắt buộc khi gọi tool mà không truyền threads_user_id và access_token. Server không thoát khi thiếu chúng, để client vẫn liệt kê được tool.
Related MCP server: mcp-threads
Lấy token
developers.facebook.com → App → thêm sản phẩm Threads API.
Cấp quyền:
threads_basic,threads_content_publish.Qua luồng OAuth Threads → lấy access token + THREADS_USER_ID.
Host API:
graph.threads.net(khác Facebook/Instagram).
Import vào Evose (STDIO / npx)
{
"mcpServers": {
"threads": {
"command": "npx",
"args": ["-y", "github:<user>/threads-mcp"],
"env": {
"THREADS_USER_ID": "...",
"THREADS_ACCESS_TOKEN": "..."
}
}
}
}Thay <user> bằng GitHub username. Execution Timeout để 120s.
Import vào Evose (HTTP remote)
Deploy server ở chế độ MCP_TRANSPORT=http (VPS/Railway/Render), sau đó khai báo trong Evose dạng Streamable HTTP:
{
"mcpServers": {
"threads": {
"url": "https://<domain-cua-server>/mcp",
"type": "streamable-http",
"headers": { "Authorization": "Bearer <MCP_AUTH_TOKEN>" }
}
}
}Ghi chú
Ảnh/video đăng từ URL công khai. License MIT.
Available Tools
9 toolsget_profileA
Lay thong tin ho so Threads (username, ten, tieu su).
Inputs: no named parameters.
get_repliesD
Lay cac reply cua mot bai.
Inputs: thread_id (required).
get_threadC
Lay chi tiet mot bai theo thread_id.
Inputs: thread_id (required).
list_threadsC
Lay danh sach bai da dang tren Threads.
Inputs: limit.
post_carouselC
Dang carousel (nhieu anh/video) len Threads.
Inputs: items (required), text.
post_imageC
Dang bai kem 1 anh len Threads tu URL anh cong khai.
Inputs: image_url (required), text.
post_textC
Dang bai text len Threads.
Inputs: text (required).
post_videoC
Dang bai kem video len Threads tu URL video cong khai.
Inputs: video_url (required), text.
replyC
Tra loi (reply) vao mot bai Threads.
Inputs: text (required), reply_to_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Publish, reply, moderate, search and read insights on your Threads (threads.com) account.
Publish and schedule Threads posts from your AI assistant.
Threads scheduler for AI agents: write, schedule and publish posts, review replies, read insights.
Schedule and publish posts to Instagram, Threads, TikTok, Facebook and Bluesky.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Instagram and Threads accounts — publish content, handle comments, view insights, search hashtags, and manage DMs through the Meta Graph API.5994 npm14MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for Meta's Threads API that enables publishing posts and reply chains, reading timelines and insights, and managing long-lived credentials with proactive refresh and safety checks.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to publish text posts to Threads, read your own posts, retrieve post insights, and check the publishing quota using the Threads API.13 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3030 npm4MIT