MindThread MCP
MindThread MCP lets an AI agent operate Threads accounts end-to-end through Meta's official API.
Read accounts, plans, permissions, usage, events, and analytics.
Manage brand material and per-account settings, including guarded bulk settings changes.
Generate 1–5 post drafts or multi-part threads using personas, material, formulas, and content rules.
Publish or schedule text, image, carousel, and video posts now or at specific/optimized times.
Manage a publishing library/queue: add, edit, reorder, archive, queue, delete, and approve items.
Configure cloud patrol keywords/persona/caps and review, approve, reject, or log drafted replies.
Read account insights, patrol performance, and recent activity.
Access playbook/formulas and handle approvals, key disabling, and connection setup with permission controls.
Enables AI agents to write, schedule, and publish Threads posts (text, images, carousels, and video), manage scheduled posts and content libraries, generate on-brand drafts, review and approve or reject drafted replies, and read account insights through Meta's official 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., "@MindThread MCP Draft a Threads post about our launch, show me, then schedule it for tomorrow at 9am"
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.
MindThread MCP: the Threads scheduler built for AI agents
Let Claude, Cursor or any MCP client write, schedule and publish Threads posts, review drafted replies and read insights for your accounts, through Meta's official Threads API. 40+ tools, a free sandbox key, and permission controls so the agent asks before it posts.
claude mcp add --transport http mindthread https://mindthread.tw/api/mcp --header "Authorization: Bearer mt_live_your_key"What your agent can do
Write: generate 1 to 5 drafts in the account's voice (persona, brand material, content formulas), or threads of 2 to 10 parts.
Schedule and publish: text, single image, carousel (2 to 10 images) or video, now or at an exact time; or drop posts into a queue that publishes at the account's own time slots.
Stay on-brand in code: content rules (length, banned phrases, no hashtags, only numbers from your fact list) are enforced by the server, not just suggested in a prompt.
Reply where it matters: cloud patrol searches Threads for your keywords and drafts replies; your agent lists the drafts and approves or rejects each one.
Measure: views, likes, replies and followers per account, plus the results of patrol replies.
Research and plan (MindThread API 1.22.0): rank the best posts of an account you connected (
get_top_posts; the Threads API only returns insights for the authorized user's own posts, so other people's accounts cannot be read) and keep brand, content and content-map documents on MindThread (save_brand_doc,get_brand_doc, last 20 versions kept).Stay in control: every key has per-permission
allow,askordeny. Withask, the post waits until you confirm it on mindthread.tw, and the agent gets a link to hand you instead of posting.
Related MCP server: threads-mcp
Three-minute setup
1. Get an API key. Sign up at mindthread.tw, connect a Threads account, then open Settings → API keys and create a key.
Start with a test key (mt_test_…): reads show your real data, writes are simulated and nothing reaches Threads. Switch to a live key (mt_live_…) when you are ready.
Every plan includes API access (October 2026: free plan 50 calls a day per live key; test keys share a 500-a-day sandbox). Current limits: mindthread.tw/developers.
2. Add MindThread to your client (pick yours below).
3. Ask for your first scheduled post:
List my MindThread accounts. Then write a short post about why I started my business, show it to me, and schedule it on my account for tomorrow at 9:00 Taipei time.
The agent calls list_accounts, generate_posts, then publish with publish_at. Check the result with "show my scheduled posts" (list_schedules).
Client setup
There are two ways to connect, and both reach the same server:
Remote (recommended): point the client at
https://mindthread.tw/api/mcp. Nothing to install.Local stdio: run this package with
npx -y mindthread-mcp. Use it for clients that only start servers with a command. It forwards every message to the same endpoint, so the tools are always identical.
Claude Code
# Remote, with an API key
claude mcp add --transport http mindthread https://mindthread.tw/api/mcp --header "Authorization: Bearer mt_live_your_key"
# Remote, signing in with your MindThread account instead of a key (run /mcp in Claude Code to log in)
claude mcp add --transport http mindthread https://mindthread.tw/api/mcp
# Local stdio
claude mcp add mindthread --env MINDTHREAD_API_KEY=mt_live_your_key -- npx -y mindthread-mcpClaude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"mindthread": {
"command": "npx",
"args": ["-y", "mindthread-mcp"],
"env": { "MINDTHREAD_API_KEY": "mt_live_your_key" }
}
}
}On Windows, if Claude cannot find npx, use "command": "cmd" and "args": ["/c", "npx", "-y", "mindthread-mcp"].
Without editing files: Settings → Connectors → Add custom connector, URL https://mindthread.tw/api/mcp, then sign in with your MindThread account (on Claude plans that offer custom connectors).
Cursor
~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"mindthread": {
"url": "https://mindthread.tw/api/mcp",
"headers": { "Authorization": "Bearer mt_live_your_key" }
}
}
}Or the stdio form: "command": "npx", "args": ["-y", "mindthread-mcp"], "env": { "MINDTHREAD_API_KEY": "mt_live_your_key" }.
VS Code (GitHub Copilot agent mode)
.vscode/mcp.json, which asks for the key once and stores it securely:
{
"inputs": [
{ "type": "promptString", "id": "mindthread-key", "description": "MindThread API key", "password": true }
],
"servers": {
"mindthread": {
"type": "http",
"url": "https://mindthread.tw/api/mcp",
"headers": { "Authorization": "Bearer ${input:mindthread-key}" }
}
}
}Any other MCP client
Streamable HTTP:
https://mindthread.tw/api/mcp, headerAuthorization: Bearer <key>(also accepted asX-API-Key).stdio: command
npx, args-y mindthread-mcp, envMINDTHREAD_API_KEY.
Without a key, initialize, tools/list, get_playbook and list_formulas still work, so you can look around first.
Example prompts
"What can MindThread do? Read the playbook first." (
get_playbook)"Write 3 posts about saving for a first home in @mybrand's voice. Don't post anything yet." (
generate_posts)"Queue posts 1 and 3; schedule post 2 for Friday 20:00." (
add_library,publish)"Any drafted replies waiting for me? Show them one by one." (
list_pending_replies,approve_pending_reply,reject_pending_reply)"How did @mybrand do in the last 7 days compared with the 7 days before?" (
analytics_insights)"Rank the 20 best posts of @mybrand by engagement and summarize my core ideas and voice into a content document." (
get_top_posts,save_brand_doc)Three Traditional Chinese prompt templates (best posts, brand interview, content map): mindthread-cli README and mindthread.tw/developers#prompt-templates.
"Set cloud patrol keywords to 'first home', 'mortgage', 'rent vs buy', at most 10 replies a day, and hold every reply for my review." (
set_cloud_patrol)
Tools
The set any client sees before signing in, generated from the live server with npm run tools-table. The server is the source of truth: when it adds a tool, this package exposes it without an update.
Tool | Title | Kind | What it does |
| My plan and key | read | Returns the current plan, this connection's identity and permissions (each permission is allow, ask or deny), remaining daily calls in this … |
| List connected accounts | read | Lists the Threads accounts connected to this MindThread member, with the id to pass as account_id to every other tool. |
| Get brand material | read | Returns the account's material digest (who the brand is, what it sells, claims, experiences, FAQ, sourced numbers, voice) that every … |
| Build brand material | write | Builds or rebuilds the account's material digest from up to 8 https pages of the brand's own website, optional notes with real cases and … |
| Get account settings | read | Returns one account's persona, schedule_times, review_before_publish, auto_reply_enabled, auto_thread, content_rules, and the guardrails … |
| Update account settings | write | Changes an account's persona (up to 4,000 characters), schedule_times (comma-separated HH:MM in the account time zone, up to 8), … |
| Guardrail change history | read | Lists an account's guardrail revisions, newest first (limit 1 to 50, default 20; before for the next page). |
| List account settings (bulk) | read | Lists every connected Threads account of this member with the settings of the MindThread bulk settings sheet (run mode, auto-posting, review … |
| Preview bulk settings changes | read | Shows what a batch of settings changes would do and writes nothing: for each account and cell the current value and the new value, warnings … |
| Apply bulk settings changes | write | Writes a batch of settings changes to up to 100 accounts, each account in its own transaction, and returns a per-row result (ok, unchanged, … |
| Undo a bulk settings batch | write | Restores the values that one batch changed, within 24 hours of the batch. |
| Get a bulk settings batch | read | Returns one batch by batch_id: when it was sent and from where (website, API or MCP), counts, whether it can still be reverted, and each … |
| Generate post drafts | write | Generates 1 to 5 post drafts about a topic using a content formula (auto, or an id from list_formulas), the account persona and material, … |
| Publish or schedule a post | write | Publishes a post to Threads now (publish_now:true) or at publish_at (ISO 8601 with offset). |
| Schedule a text post | write | Schedules an existing text (up to 500 characters) at publish_at, or at the next best slot with auto_optimize_time:true (the two are mutually … |
| List scheduled posts | read | Lists scheduled posts, optionally filtered by account_id, with status, publish_at, and held_reason when a post was held (for example … |
| Cancel a scheduled post | write | Cancels a scheduled post by id. |
| List library items | read | Lists an account's library items by status (queued, draft, published, failed; limit up to 200). |
| Add library items | write | Adds up to 20 items (text, optional public https images) to an account's library as queued (default; they publish automatically at … |
| Delete a library item | write | Permanently deletes one queued, draft or archived library item by id. |
| Approve a draft into the queue | write | Moves one draft into the publishing queue by id. |
| Update a library item | write | Changes one library item by id: status (archived, draft, queued), text (checked against content_rules), or its place in the queue (position … |
| Get cloud patrol settings | read | Returns an account's cloud patrol configuration and status: keywords, daily cap, replies sent today, review_before_reply, last scan time. |
| Set cloud patrol | write | Creates or updates an account's cloud patrol: keywords (1 to 10; a "#tag" entry searches a topic tag), reply persona, daily_cap (1 to 50 on … |
| Cloud patrol reply log | read | Lists replies sent by cloud patrol for an account in the last 1 to 7 days, with the target post and the reply text. |
| Cloud patrol results | read | Returns views and likes earned by cloud patrol replies for an account over 1 to 14 days, with the top replies. |
| List drafted replies awaiting review | read | Lists cloud patrol reply drafts for an account by status (pending by default; also sent, rejected, expired). |
| Send a drafted reply | write | Approves one drafted cloud patrol reply by id and sends it to Threads now, optionally with an edited reply text that passes the same quality … |
| Reject a drafted reply | write | Rejects one drafted cloud patrol reply by id with an optional note. |
| List recent events | read | Returns the member's event feed for the last 7 days, newest first (limit 1 to 200): post.published, post.failed, reply.sent, patrol.reply, … |
| Account insights | read | Returns views, likes, replies and followers for one account over a period (7d, 30d; default 30d). |
| List content formulas | read | Lists the content formulas that generate_posts accepts, with id and a short description of each. |
| Operating playbook | read | Returns the operating playbook for running an account through this server: the daily loop, how confirmation requests work, quotas, and the … |
| Get a link to connect a new account | write | Returns a Threads OAuth link for the user to open in a browser to connect a new Threads account to this member. |
| Disable this connection | write | Permanently disables the key or connection making this call. |
| My usage and call log | read | Returns this connection's own usage for the last 1 to 30 days (days=1 is today since 00:00 Asia/Taipei): summary (calls, units, errors, … |
| Check a confirmation request | read | Returns one confirmation request created by this connection, by id (apr_...): status (pending, approved, executed, failed, denied, expired, … |
| Archive library items in bulk | write | Archives up to 50 library items by id in one call. |
| Delete library items in bulk | write | Permanently deletes up to 50 queued, draft or archived library items by id in one call. |
| Queue library items in bulk | write | Moves up to 50 drafts into the publishing queue by id in one call; they publish automatically at the account's schedule_times. |
Safety and control
Permissions per key. Each permission (read, write drafts, schedule, publish now, send replies, turn cloud patrol on, connect accounts, loosen guardrails, webhooks) is
allow,askordeny, set in Settings → API keys.askmeans the agent receivesapproval_requiredwith a link for you; the action runs only after you confirm on mindthread.tw.Things only you do on the website. Undoing a guardrail change is always yours. Turning cloud patrol on is never granted to an OAuth connection (Claude, ChatGPT), and an API key needs that permission set explicitly.
Content rules run in code.
enforce: "block"makes the server refuse a post that breaks the rules, whatever the model wrote.Kill switch.
disable_this_keypermanently disables the key in use. You can also revoke keys and connections in Settings.Official API only. Posting and replies go through Meta's official Threads API. MindThread never asks for your Threads password.
Your key stays local. In stdio mode the key is read from the
MINDTHREAD_API_KEYenvironment variable and sent only tomindthread.tw. It is never printed (logs showmt_live_…abcd).
Configuration
Variable | Required | Meaning |
| for any tool that touches your accounts |
|
| no | Endpoint override, default |
Requires Node.js 18.17 or newer. No runtime dependencies.
Troubleshooting
"MINDTHREAD_API_KEY is not set": add the key to the
envblock of this server in your client config, then restart the client."MindThread rejected the key": the key is wrong, revoked or disabled. Create a new one in Settings → API keys.
approval_required: working as intended. Open the link the agent shows you, confirm, and the post goes out.insufficient_scope: that permission is set todenyfor this key. The error'sfixfield names the setting to change.rate_limit_exceeded: daily or per-minute limit reached; the error says when it resets. Every tool call counts against the key's daily quota, polls included (list_events,list_pending_replies): on the free plan (50 calls a day) poll every 30 minutes or slower, or use a webhook. After a daily limit the bridge holds tool calls until the reset (00:00 Asia/Taipei) and answers them itself with the same error (held_locally: true), so an agent loop cannot keep hitting MindThread;get_playbook,list_formulas,get_approvalanddisable_this_keystill go through.Logs go to stderr (Claude Desktop: Settings → Developer → Open Logs Folder). stdout carries only MCP messages.
Also available
CLI for scripts and agents that prefer shell commands: mindthread-cli (
npx mindthread-cli).REST API: OpenAPI 3.1 at mindthread.tw/api/v1/openapi.json, docs at mindthread.tw/developers, agent guide at mindthread.tw/llms.txt.
繁體中文
MindThread 是給 AI agent 用的 Threads 排程器。接上之後,Claude、Cursor 或任何支援 MCP 的工具,都能替你的 Threads 帳號寫文、排程、發文(文字、單圖、輪播、影片)、審核雲端海巡的回覆草稿、看觀看與互動數據。全程走 Meta 官方 Threads API,不需要你的 Threads 密碼。
三分鐘上手:
到 mindthread.tw 註冊並連接 Threads 帳號,在「設定 → API 金鑰」建立金鑰。建議先用測試金鑰(
mt_test_開頭):讀取的是真資料,寫入只模擬、不會發到 Threads。把 MindThread 加進你的工具,例如 Claude Code:
claude mcp add --transport http mindthread https://mindthread.tw/api/mcp --header "Authorization: Bearer mt_live_你的金鑰"Claude Desktop、Cursor、VS Code 的設定見上方 Client setup。
對 AI 說:「列出我的 MindThread 帳號,幫我寫一篇介紹我為什麼創業的短文,給我看過之後,排在明天早上 9 點發。」
你保有控制權:每把金鑰的每項權限都能設成「允許」「先問我」「拒絕」。設成「先問我」時,AI 會拿到一個確認連結交給你,你在 mindthread.tw 按下確認才會發出。字數、禁用詞、只能用你列的數字這些內容規則,由伺服器以程式檢查,可以設成直接擋下。
在 Claude 裡直接研究、規劃、排程你的 Threads:把 MindThread MCP 接上 Claude 或 ChatGPT 之後,get_top_posts 會從你自己連結的帳號抓出互動最好的貼文(Threads 官方 API 只開放讀授權者本人的成效,讀不到別人的帳號),save_brand_doc 和 get_brand_doc 幫你把品牌文件、內容文件、內容地圖存在 MindThread(保留最近 20 版),generate_posts 照你的人設起草,schedule_text 或 add_library 排進發文時段。整理、規劃、起草、排程,都在同一段對話裡完成;每一步要不要存、要不要排,由你決定。三個繁中提示詞範本(整理最佳貼文、品牌訪談、內容地圖)見 mindthread.tw/developers#prompt-templates。
License
MIT © Ultra Lab
Available Tools
40 toolsadd_libraryAdd library itemsADestructiveInspect
Adds up to 20 items (text, optional public https images) to an account's library as queued (default; they publish automatically at schedule_times) or draft (they wait). Each text is checked against the account's content_rules. Applies after drafts are approved by the user and should enter the daily publishing queue, or should be parked as drafts.
Inputs: items (required), account_id (required), status.
analytics_insightsAccount insightsARead-onlyIdempotentInspect
Returns views, likes, replies and followers for one account over a period (7d, 30d; default 30d). account_id is required; "all" returns the organization-wide aggregate. views_scope is lifetime, posts_scope is the period. Applies when the user asks how an account is performing.
Inputs: account_id (required), period.
apply_account_settingsApply bulk settings changesADestructiveIdempotentInspect
Writes a batch of settings changes to up to 100 accounts, each account in its own transaction, and returns a per-row result (ok, unchanged, or failed with the reason) and a batch_id that revert_account_settings_batch can undo within 24 hours. idempotency_key is required: a retried request with the same key returns the first result instead of writing twice. Changes to run mode, auto-posting or review before publish affect posting right away and need confirm_sensitive:true, and that confirmation may wait for the owner's approval. Nothing is written without a preview: from a Claude or ChatGPT connection the preview_id from preview_account_settings is required, and a preview_id that does not match the changes is refused. Applies after the user has seen the preview and confirmed it. 繁中:套用批次變更(每帳號一個交易、24 小時內可復原),敏感欄位要 confirm_sensitive,目錄連線一定要先預覽並帶 preview_id。
Inputs: idempotency_key (required), csv, reason, changes, +2 more.
approve_library_itemApprove a draft into the queueADestructiveIdempotentInspect
Moves one draft into the publishing queue by id. A draft whose held_reason is publish_result_unknown answers 409 publish_result_unknown because it may already be on Threads; an item being published answers 409 publishing_in_progress. Applies when the user approves a single draft.
Inputs: id (required).
approve_pending_replySend a drafted replyADestructiveInspect
Approves one drafted cloud patrol reply by id and sends it to Threads now, optionally with an edited reply text that passes the same quality gates as generated text. May wait for the owner's confirmation. Applies when the user has read a pending draft and wants it posted.
Inputs: id (required), reply.
build_materialBuild brand materialADestructiveInspect
Builds or rebuilds the account's material digest from up to 8 https pages of the brand's own website, optional notes with real cases and FAQs (up to 6,000 characters), and the account's top posts. Replaces the previous digest. Counts as one AI generation. dry:true returns a preview without saving. Applies once per account before the first generation, and again when the website changes.
Inputs: account_id (required), dry, urls, notes.
bulk_archive_libraryArchive library items in bulkAIdempotentInspect
Archives up to 50 library items by id in one call. Archived items leave the queue but are kept and can be restored with update_library_item. Per-item errors include publishing_in_progress. Applies for clearing a queue without deleting anything.
Inputs: ids (required).
bulk_delete_libraryDelete library items in bulkADestructiveIdempotentInspect
Permanently deletes up to 50 queued, draft or archived library items by id in one call. Per-item errors include publishing_in_progress. Applies when the user explicitly wants items removed for good.
Inputs: ids (required).
bulk_queue_libraryQueue library items in bulkADestructiveIdempotentInspect
Moves up to 50 drafts into the publishing queue by id in one call; they publish automatically at the account's schedule_times. Per-item errors include publishing_in_progress and publish_result_unknown (the item may already be on Threads). Applies when the user approves several drafts at once.
Inputs: ids (required).
cancel_scheduleCancel a scheduled postADestructiveIdempotentInspect
Cancels a scheduled post by id. A post that is being published right now answers 409 publishing_in_progress. Applies when the user no longer wants a scheduled post to go out.
Inputs: id (required).
cloud_patrol_logCloud patrol reply logARead-onlyIdempotentInspect
Lists replies sent by cloud patrol for an account in the last 1 to 7 days, with the target post and the reply text. Applies when the user wants to read what was actually said.
Inputs: account_id (required), days.
cloud_patrol_statsCloud patrol resultsARead-onlyIdempotentInspect
Returns views and likes earned by cloud patrol replies for an account over 1 to 14 days, with the top replies. Applies when the user asks whether patrol is working or which keywords perform.
Inputs: account_id (required), days.
connect_account_linkGet a link to connect a new accountAInspect
Returns a Threads OAuth link for the user to open in a browser to connect a new Threads account to this member. The account appears in list_accounts after the user completes the flow. May wait for the owner's confirmation. Applies when the user wants to add an account.
Inputs: no named parameters.
delete_library_itemDelete a library itemADestructiveIdempotentInspect
Permanently deletes one queued, draft or archived library item by id. Applies when the user explicitly wants an item gone rather than archived.
Inputs: id (required).
disable_this_keyDisable this connectionADestructiveIdempotentInspect
Permanently disables the key or connection making this call. Cannot be undone; the owner creates a new key or reconnects in Settings. Only this connection's API requests stop, and for a connection made through the consent page (OAuth) the webhooks it created are turned off too; queued posts and cloud patrol settings created with it keep running (with an API key, its webhooks keep running as well). The result lists the confirmation requests this connection was still waiting on, now cancelled. Every later call with it answers 401 key_disabled. A connection made through the consent page of a platform such as claude.ai or ChatGPT is shared by every session of that platform for this member, so disabling it stops all of them until the user reconnects. Applies when the credential may have leaked or the user asks to stop this connection for good.
Inputs: no named parameters.
generate_postsGenerate post draftsAInspect
Generates 1 to 5 post drafts about a topic using a content formula (auto, or an id from list_formulas), the account persona and material, optional reference context (up to 8,000 characters) and a quality level (fast, standard, premium). Nothing is published or queued. The result carries rule_violations against the account's content_rules. Applies when the user wants drafts to read, edit or choose from.
Inputs: topic (required), count, context, formula, +2 more.
get_account_settingsGet account settingsARead-onlyIdempotentInspect
Returns one account's persona, schedule_times, review_before_publish, auto_reply_enabled, auto_thread, content_rules, and the guardrails block: etag (used as if_match on update), last_change, pending loosening approvals, and which paths the rules are enforced on. Applies before any settings change, because content_rules is replaced as a whole on update.
Inputs: account_id (required).
get_account_settings_batchGet a bulk settings batchARead-onlyIdempotentInspect
Returns one batch by batch_id: when it was sent and from where (website, API or MCP), counts, whether it can still be reverted, and each row's result with the failure reason. Applies after apply_account_settings, or when the user asks what a bulk change did. 繁中:查一批變更的逐列結果。
Inputs: batch_id (required).
get_approvalCheck a confirmation requestARead-onlyIdempotentInspect
Returns one confirmation request created by this connection, by id (apr_...): status (pending, approved, executed, failed, denied, expired, cancelled), the action summary, how the owner decided (decision_via, decided_by, step_up), and once executed, the full result. The server runs the original request itself after the owner confirms, so the request is not resent. Applies after a tool answered approval_required, polling about every 15 seconds until the status is final (pending requests expire after 24 hours).
Inputs: id (required).
get_cloud_patrolGet cloud patrol settingsARead-onlyIdempotentInspect
Returns an account's cloud patrol configuration and status: keywords, daily cap, replies sent today, review_before_reply, last scan time. Cloud patrol searches Threads every 15 minutes and replies to relevant fresh posts through the official API. Applies before changing patrol settings or when the user asks whether patrol is on.
Inputs: account_id (required).
get_materialGet brand materialARead-onlyIdempotentInspect
Returns the account's material digest (who the brand is, what it sells, claims, experiences, FAQ, sourced numbers, voice) that every generation path appends to the persona. has_material:false means generation currently runs on the persona alone. Applies before generating when it is unclear whether the account has material.
Inputs: account_id (required).
get_meMy plan and keyARead-onlyIdempotentInspect
Returns the current plan, this connection's identity and permissions (each permission is allow, ask or deny), remaining daily calls in this connection's pool, remaining patrol points, and the connected accounts. Applies at the start of a session and whenever a call answered approval_required or insufficient_scope, to see which permission is involved.
Inputs: no named parameters.
get_my_usageMy usage and call logARead-onlyIdempotentInspect
Returns this connection's own usage for the last 1 to 30 days (days=1 is today since 00:00 Asia/Taipei): summary (calls, units, errors, by_endpoint) and recent calls (request_id, endpoint, status, units, at), newest first, limit 1 to 100, cursor for the next page. Only this connection's records. Applies when the user asks what this connection did, or a request_id is needed to report a problem.
Inputs: days, limit, cursor.
get_playbookOperating playbookARead-onlyIdempotentInspect
Returns the operating playbook for running an account through this server: the daily loop, how confirmation requests work, quotas, and the review checklist. The same text is in the initialize instructions. Applies when the instructions were not kept or the user asks how the service works.
Inputs: no named parameters.
list_accountsList connected accountsARead-onlyIdempotentInspect
Lists the Threads accounts connected to this MindThread member, with the id to pass as account_id to every other tool. Applies whenever an account id is needed and the user named an account by username or description.
Inputs: no named parameters.
list_account_settingsList account settings (bulk)ARead-onlyIdempotentInspect
Lists every connected Threads account of this member with the settings of the MindThread bulk settings sheet (run mode, auto-posting, review before publish, posting times, audience time zone, random schedule, library recycling, cold start, content language, AI quality, auto-reply and reply limits) and status chips (expired authorization, repeated publish failures, skipped nightly refill). Up to 100 accounts per page, with limit and cursor for more. columns describes each setting (type, allowed values, which ones are sensitive) and rules_url links to the field rules page. Applies when the user wants to see or compare settings across many accounts. 繁中:列出所有帳號的總表設定與狀態標籤。
Inputs: limit, cursor.
list_eventsList recent eventsARead-onlyIdempotentInspect
Returns the member's event feed for the last 7 days, newest first (limit 1 to 200): post.published, post.failed, reply.sent, patrol.reply, patrol.pending, token.expiring, usage.threshold, approval.decided. since (ISO 8601) returns only newer events; types filters by name. Applies when the user asks what happened recently or whether a post went out.
Inputs: limit, since, types.
list_formulasList content formulasARead-onlyIdempotentInspect
Lists the content formulas that generate_posts accepts, with id and a short description of each. Applies when the user wants a specific structure (for example a story, a list, a myth-busting post) rather than auto.
Inputs: no named parameters.
list_guardrail_changesGuardrail change historyARead-onlyIdempotentInspect
Lists an account's guardrail revisions, newest first (limit 1 to 50, default 20; before for the next page). Each revision has source (api, approval, rollback, system), actor, changed_fields, loosened, tightened, before, after and restore_body (an update_account_settings body that puts the earlier values back). Applies when the user asks what changed, who changed it, or wants to restore an earlier rule set.
Inputs: account_id (required), limit, before.
list_libraryList library itemsARead-onlyIdempotentInspect
Lists an account's library items by status (queued, draft, published, failed; limit up to 200). Queued items publish automatically at the account's schedule_times; the result shows each item's position and next_publish_at. A draft with held_reason publish_result_unknown and reclaimed:true may already be on Threads. Applies when the user asks what is queued, what is waiting as a draft, or what failed.
Inputs: account_id (required), limit, status.
list_pending_repliesList drafted replies awaiting reviewARead-onlyIdempotentInspect
Lists cloud patrol reply drafts for an account by status (pending by default; also sent, rejected, expired). Each pending draft has the target post, the drafted reply and an expiry 24 hours after it was drafted. Applies when review_before_reply is on and the user wants to decide what goes out.
Inputs: account_id (required), status.
list_schedulesList scheduled postsARead-onlyIdempotentInspect
Lists scheduled posts, optionally filtered by account_id, with status, publish_at, and held_reason when a post was held (for example content_rules_violated or publish_result_unknown). Applies when the user asks what is coming up or why a post did not go out.
Inputs: account_id.
preview_account_settingsPreview bulk settings changesARead-onlyIdempotentInspect
Shows what a batch of settings changes would do and writes nothing: for each account and cell the current value and the new value, warnings (for example no posting time left), and row errors (an account that is not this member's, an unknown column, a value outside the allowed range, a cell changed since it was read). Takes changes as a list of { account_id, set, base } or csv in the same format as the website download. The result carries apply_changes and a preview_id valid for 15 minutes, which apply_account_settings takes as they are. Applies before any bulk change, so the user sees the exact cells first. 繁中:預覽批次變更,逐格列出舊值與新值,什麼都不寫。
Inputs: csv, changes.
publishPublish or schedule a postADestructiveInspect
Publishes a post to Threads now (publish_now:true) or at publish_at (ISO 8601 with offset). Takes text, one public https image (media_urls with 1 url), a carousel (2 to 10 urls) or a video_url. Text over 500 characters is split into a thread. Publishing now or within 30 minutes uses the publish-now permission; a post 30 minutes or more ahead uses the schedule permission. Either may wait for the owner's confirmation when that permission is set to ask on this connection. idempotency_key makes a retried request return the first result instead of posting twice. Applies when the user has final text and wants it on Threads.
Inputs: account_id (required), text, video_url, media_urls, +3 more.
reject_pending_replyReject a drafted replyADestructiveIdempotentInspect
Rejects one drafted cloud patrol reply by id with an optional note. It is never sent and the same post is not proposed again. Applies when the user does not want a drafted reply to go out.
Inputs: id (required), reason.
revert_account_settings_batchUndo a bulk settings batchADestructiveInspect
Restores the values that one batch changed, within 24 hours of the batch. Accounts changed again after the batch are skipped and listed with the reason, so a later edit is never overwritten. A batch can be reverted once. Applies when the user wants to undo a bulk change. 繁中:24 小時內復原一批變更,之後又被改過的帳號會跳過。
Inputs: batch_id (required).
schedule_textSchedule a text postADestructiveInspect
Schedules an existing text (up to 500 characters) at publish_at, or at the next best slot with auto_optimize_time:true (the two are mutually exclusive). Checked against the account's content_rules: with enforce:block a violation returns 422 and nothing is scheduled; the post is checked again right before it publishes. Applies for text-only posts with a specific time or when the user wants the system to pick the time.
Inputs: text (required), account_id (required), publish_at, schedule_at, +1 more.
set_cloud_patrolSet cloud patrolADestructiveIdempotentInspect
Creates or updates an account's cloud patrol: keywords (1 to 10; a "#tag" entry searches a topic tag), reply persona, daily_cap (1 to 50 on free and trial, up to 80 on paid plans, up to 150 with a haixun add-on), enabled, and review_before_reply. When patrol is on, the account replies to relevant fresh Threads posts through the official API every 15 minutes, one patrol point per delivered reply; with review_before_reply:true every drafted reply waits in list_pending_replies instead of going out. Turning patrol on, or changing a patrol that is already on, needs the patrol permission, which is not granted to directory connections: the owner does it in MindThread. Applies when the user wants to stop patrol or tune its keywords, persona and cap while it is off.
Inputs: account_id (required), mode, enabled, persona, +3 more.
update_account_settingsUpdate account settingsADestructiveIdempotentInspect
Changes an account's persona (up to 4,000 characters), schedule_times (comma-separated HH:MM in the account time zone, up to 8), review_before_publish, auto_reply_enabled, auto_thread, auto_link_to_comment, enabled, and content_rules (max_chars, min_chars, forbid_cta, forbid_hashtags, banned_phrases, facts as the only numbers the AI may use, forbid_causal_claims, judge_claims, one_fact_per_post, mention_limits, enforce warn or block). Only the fields sent are changed, except content_rules, which is replaced as a whole. if_match (the guardrails etag) makes a concurrent change answer 412 instead of overwriting; reason (up to 200 characters) is stored in the revision; dry_run:true previews whether the change would apply, ask the owner or be denied, without writing anything. A change that loosens a guardrail may wait for the owner's confirmation. Applies when the user asks to change voice, posting times, review mode, auto-reply or content rules.
Inputs: account_id (required), reason, dry_run, enabled, +8 more.
update_library_itemUpdate a library itemADestructiveIdempotentInspect
Changes one library item by id: status (archived, draft, queued), text (checked against content_rules), or its place in the queue (position first or last, or an explicit order). 409 publishing_in_progress means it is being published; 409 publish_result_unknown means it may already be on Threads; 409 status_changed means it changed since it was read. Applies when the user wants to edit, reorder, archive or restore one item.
Inputs: id (required), text, order, status, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 40 tools
The tools cover many distinct resources, but several adjacent workflows overlap: single vs bulk settings writes (update_account_settings, preview_account_settings, apply_account_settings), multiple ways to queue a draft (approve_library_item, bulk_queue_library, update_library_item), and multiple posting paths (publish, schedule_text, add_library). The long descriptions do clarify most boundaries, so an agent can usually recover, but tool-name-level disambiguation is weaker than ideal.
Most names are readable snake_case, but the conventions are mixed: verb_noun actions, bulk_* prefixes, noun-only tools such as analytics_insights and cloud_patrol_stats, and the bare verb publish. The naming is still interpretable, but it is not a predictable verb_noun pattern throughout.
At 40 tools, this is well above a focused tool surface and falls into the too-many category even for a broad account-management domain. Many operations are justified individually, but the set carries substantial workflow branching that increases agent selection cost.
Coverage is broad: account connection, material, settings and guardrails, content generation, publishing, scheduling, library management, cloud patrol, analytics, events, approvals, and usage. Minor gaps remain, such as no explicit account disconnect/delete flow and no way to delete or edit already-published posts.
Maintenance
Related MCP Connectors
Publish and schedule Threads posts from your AI assistant.
Publish, reply, moderate, search and read insights on your Threads (threads.com) account.
Lets AI agents post and reply on Instagram, TikTok, Threads and more, with a human approval queue.
Publish and schedule Bluesky posts and threads from your AI assistant.
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
- FlicenseBqualityCmaintenanceEnables posting and managing Threads content via Meta Threads API, including text, image, video, carousel, and replies.9-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with Meta Threads by fetching profile details, recent posts, post and account analytics, and conversation reply trees, as well as exporting posts as JSON for archiving or embedding.7-
- AlicenseAqualityBmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3030 npm4MIT