# MindThread (remote · mindthread.tw)

Threads scheduler for AI agents: write, schedule and publish posts, review replies, read insights.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mindthread.tw`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ppcvote-mindthread/api-mcp.md), [page](https://verifymcp.io/servers/ppcvote-mindthread/api-mcp)
- npm · `mindthread-mcp`: 39/100, [markdown](https://verifymcp.io/servers/ppcvote-mindthread/mindthread-mcp.md), [page](https://verifymcp.io/servers/ppcvote-mindthread/mindthread-mcp)

## Channel facts

- Endpoint: `https://mindthread.tw/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (build_material).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6394 tokens (~148/item across 43 items; 43 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 44 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MindThread MCP server?

MindThread is a hosted endpoint at https://mindthread.tw/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ppcvote-mindthread 'https://mindthread.tw/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ppcvote-mindthread": {
      "url": "https://mindthread.tw/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ppcvote-mindthread": {
      "type": "http",
      "url": "https://mindthread.tw/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ppcvote-mindthread]
url = "https://mindthread.tw/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ppcvote-mindthread": {
      "type": "remote",
      "url": "https://mindthread.tw/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ppcvote-mindthread --url 'https://mindthread.tw/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ppcvote-mindthread:
    url: "https://mindthread.tw/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ppcvote-mindthread": {
      "Transport": "http",
      "Url": "https://mindthread.tw/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ppcvote-mindthread -t streamable-http -u 'https://mindthread.tw/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ppcvote-mindthread": {
      "type": "http",
      "url": "https://mindthread.tw/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +1)

- [security] New tool “save_brand_doc”, which the server declares destructive
- [functional] Server version: 1.21.0 → 1.22.0
- [functional] New tool “get_top_posts”
- [functional] New tool “get_brand_doc”

### 2026-11-03 (score 70, +1)

- [security] Tool “list_events” rewrote its description, which is the text the model reads
- [security] Tool “list_pending_replies” rewrote its description, which is the text the model reads

### 2026-10-31 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 68, 0)

- [security] Tool “update_account_settings” rewrote its description, which is the text the model reads
- [functional] Server version: 1.20.0 → 1.21.0
- [cosmetic] “update_account_settings” added an optional parameter “random_schedule”
- [cosmetic] “set_cloud_patrol” added an optional parameter “reply_max”
- [cosmetic] “update_account_settings” added an optional parameter “random_exclude”
- [cosmetic] “update_account_settings” added an optional parameter “random_per_day”
- [cosmetic] “update_account_settings” added an optional parameter “random_window”

### 2026-10-29 (score 68, +1)

- [functional] Server version: 1.19.0 → 1.20.0
- [cosmetic] “set_cloud_patrol” added an optional parameter “rotate_replies”
- [cosmetic] “set_cloud_patrol” added an optional parameter “reply_mode”

### 2026-10-27 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.16.1 → 1.19.0

### 2026-10-26 (score 66)

First indexed and scored.

## MCP tools (43)

### `get_me` (~72 tokens)

My plan and key

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.

### `list_accounts` (~50 tokens)

List connected accounts

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.

### `get_material` (~80 tokens)

Get brand material

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.

Input parameters:

- `account_id` (string, required): Account id

### `build_material` (~141 tokens)

Build brand material

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.

Input parameters:

- `account_id` (string, required): Account id
- `dry` (boolean): Preview only
- `notes` (string): Real experiences, cases, FAQs (≤6000 chars)
- `urls` (array): Up to 8 https:// pages

### `get_account_settings` (~92 tokens)

Get account settings

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.

Input parameters:

- `account_id` (string, required): Account id

### `update_account_settings` (~632 tokens)

Update account settings

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, random posting (random_schedule, random_per_day, random_window, and random_exclude: up to 3 ranges such as 17:00-18:00 that random times skip), 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.

Input parameters:

- `account_id` (string, required): Account id
- `auto_link_to_comment` (boolean): Links go to first comment
- `auto_reply_enabled` (boolean): AI replies to comments on own posts
- `auto_thread` (boolean): Auto-split >500 chars
- `content_rules` (object): Structured rules: max_chars, min_chars, forbid_cta, forbid_hashtags, banned_phrases[], facts[] (allowed numbers as plain sentences), forbid_causal_claims, judge_claims (model reviews for unsupported…
- `dry_run` (boolean): true = preview only (1.9.0); at most 10 a minute per key
- `enabled` (boolean): Master switch
- `if_match` (string): guardrails.etag from get_account_settings (optional, 1.9.0)
- `persona` (string): Brand persona, up to 4000 chars
- `random_exclude` (array): Up to 3 HH:MM-HH:MM ranges random times skip, no midnight crossing, no overlap; [] clears
- `random_per_day` (integer): Random posts per day, 1-30
- `random_schedule` (boolean): Random times every day instead of schedule_times (1.21.0)
- `random_window` (string): HH:MM-HH:MM, start before end; 00:00-23:59 = whole day
- `reason` (string): Why, up to 200 chars (optional, 1.9.0)
- `review_before_publish` (boolean): AI drafts wait for approval
- `schedule_times` (string): Comma-separated HH:MM, up to 8

### `list_guardrail_changes` (~139 tokens)

Guardrail change history

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.

Input parameters:

- `account_id` (string, required): Account id
- `before` (string): next_before from the previous page
- `limit` (integer): 1-50 (default 20)

### `list_account_settings` (~187 tokens)

List account settings (bulk)

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. 繁中：列出所有帳號的總表設定與狀態標籤。

Input parameters:

- `cursor` (string): next_cursor from the previous page
- `limit` (integer): 1-100, default 100

### `preview_account_settings` (~252 tokens)

Preview bulk settings changes

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. 繁中：預覽批次變更，逐格列出舊值與新值，什麼都不寫。

Input parameters:

- `changes` (array): Up to 100 entries: { account_id, set: { column: value }, base?: { column: value you saw } }. Columns and allowed values: list_account_settings columns, or https://mindthread.tw/accounts/bulk/rules
- `csv` (string): Instead of changes: a CSV in the website download format (UTF-8), up to 1 MB

### `apply_account_settings` (~384 tokens)

Apply bulk settings changes

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。

Input parameters:

- `changes` (array): Up to 100 entries: { account_id, set: { column: value }, base?: { column: value you saw } }. Columns and allowed values: list_account_settings columns, or https://mindthread.tw/accounts/bulk/rules
- `confirm_sensitive` (boolean): true when the batch changes run mode, auto-posting or review before publish
- `csv` (string): Instead of changes: a CSV in the website download format (UTF-8)
- `idempotency_key` (string, required): 8-200 characters; reuse the same key when retrying the same request
- `preview_id` (string): preview_id from preview_account_settings (required from Claude and ChatGPT connections)
- `reason` (string): Optional note stored with the batch, up to 200 characters

### `revert_account_settings_batch` (~110 tokens)

Undo a bulk settings batch

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 小時內復原一批變更，之後又被改過的帳號會跳過。

Input parameters:

- `batch_id` (string, required): batch_id from apply_account_settings

### `get_account_settings_batch` (~96 tokens)

Get a bulk settings batch

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. 繁中：查一批變更的逐列結果。

Input parameters:

- `batch_id` (string, required): batch_id from apply_account_settings

### `generate_posts` (~172 tokens)

Generate post drafts

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.

Input parameters:

- `account_id` (string): Persona source
- `context` (string): Reference material up to 8000 chars
- `count` (integer): 1-5
- `formula` (string): auto or a formula id from list_formulas
- `quality` (string): fast | standard | premium
- `topic` (string, required): What to write about

### `publish` (~241 tokens)

Publish or schedule a post

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.

Input parameters:

- `account_id` (string, required): Account id
- `idempotency_key` (string): Optional
- `media_urls` (array): Public https image URLs (1 = image, 2-10 = carousel)
- `publish_at` (string): ISO 8601 if not publish_now
- `publish_now` (boolean): Publish immediately
- `text` (string): Post text / caption
- `video_url` (string): Public https MP4/MOV

### `schedule_text` (~164 tokens)

Schedule a text post

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.

Input parameters:

- `account_id` (string, required): Account id
- `auto_optimize_time` (boolean): Next best slot (mutually exclusive with publish_at)
- `publish_at` (string): ISO 8601 with offset (canonical time field)
- `schedule_at` (string): Deprecated alias of publish_at
- `text` (string, required): Text

### `list_schedules` (~75 tokens)

List scheduled posts

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.

Input parameters:

- `account_id` (string): Filter by account

### `cancel_schedule` (~54 tokens)

Cancel a scheduled post

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.

Input parameters:

- `id` (string, required): Post id

### `list_library` (~125 tokens)

List library items

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.

Input parameters:

- `account_id` (string, required): Account id
- `limit` (integer): max 200
- `status` (string): queued | draft | published | failed

### `add_library` (~110 tokens)

Add library items

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.

Input parameters:

- `account_id` (string, required): Account id
- `items` (array, required): Items
- `status` (string): queued (default) | draft

### `delete_library_item` (~45 tokens)

Delete a library item

Permanently deletes one queued, draft or archived library item by id. Applies when the user explicitly wants an item gone rather than archived.

Input parameters:

- `id` (string, required): Item id

### `approve_library_item` (~71 tokens)

Approve a draft into the queue

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.

Input parameters:

- `id` (string, required): Item id

### `update_library_item` (~150 tokens)

Update a library item

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.

Input parameters:

- `id` (string, required): Item id
- `order` (integer): Explicit order
- `position` (string): first | last
- `status` (string): archived | draft | queued
- `text` (string): New text

### `get_cloud_patrol` (~81 tokens)

Get cloud patrol settings

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.

Input parameters:

- `account_id` (string, required): Account id

### `set_cloud_patrol` (~492 tokens)

Set cloud patrol

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.

Input parameters:

- `account_id` (string, required): Account id
- `daily_cap` (integer): reply: 1-50 free/trial, up to 80 paid, up to 150 with add-on; discover: 1 to plan daily haixun points (default)
- `enabled` (boolean): Start / stop
- `keywords` (array): 1-10 entries; "#tag" = topic-tag search
- `mode` (string): "reply" (default): AI drafts and posts replies. "discover": only list matching posts for you to read; no AI, nothing posted
- `persona` (string): Reply persona
- `reply_max` (integer): Max characters per reply, 20-200, or null for the language default. A persona asking for a length is followed up to this limit
- `reply_mode` (string): "ai" (default): AI writes each reply in the persona. "rotate": post your fixed replies in order, word for word, starting over after the last (AI still decides which posts to reply to). "consume": lik…
- `review_before_reply` (boolean): Hold drafts for approval
- `rotate_replies` (array): 1-10 fixed replies used in order when reply_mode is "rotate"; each within the account reply length limit; changing them restarts from the first

### `cloud_patrol_log` (~71 tokens)

Cloud patrol reply log

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.

Input parameters:

- `account_id` (string, required): Account id
- `days` (integer): 1-7

### `cloud_patrol_stats` (~70 tokens)

Cloud patrol results

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.

Input parameters:

- `account_id` (string, required): Account id
- `days` (integer): 1-14

### `list_pending_replies` (~111 tokens)

List drafted replies awaiting review

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. Each call counts against the daily quota even when nothing is pending. Applies when review_before_reply is on and the user wants to decide what goes out.

Input parameters:

- `account_id` (string, required): Account id
- `status` (string): pending (default) | sent | rejected | expired

### `approve_pending_reply` (~81 tokens)

Send a drafted reply

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.

Input parameters:

- `id` (string, required): Pending id
- `reply` (string): Optional edited reply

### `reject_pending_reply` (~68 tokens)

Reject a drafted reply

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.

Input parameters:

- `id` (string, required): Pending id
- `reason` (string): Optional note

### `list_events` (~151 tokens)

List recent events

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. Each call counts against the daily quota even when nothing is new, so poll sparingly (every 30 minutes on the free plan). Applies when the user asks what happened recently or whether a post went out.

Input parameters:

- `limit` (integer): 1-200
- `since` (string): ISO 8601
- `types` (string): Comma-separated event names

### `get_top_posts` (~201 tokens)

Get top posts

Returns the best posts of a Threads account this member connected, ranked by engagement (likes + replies + reposts + quotes) or by views, likes, replies, reposts or quotes, with each post's text and metrics from MindThread's insights cache. Other people's accounts cannot be read: the Threads API only returns insights for the authorized user's own posts. Applies when the user wants to study what worked on their own account, for example to write a content document. 繁中：只讀會員自己連結的帳號，依互動排序取表現最好的貼文。

Input parameters:

- `account_id` (string, required): Account id from list_accounts (only accounts this member connected)
- `days` (integer): Only posts from the last N days, 1-365 (omit = all fetched posts)
- `limit` (integer): 1-50, default 20
- `metric` (string): Ranking metric, default engagement

### `save_brand_doc` (~255 tokens)

Save a brand document

Saves a brand, content or content-map document (Markdown or plain text, up to 50,000 characters) under a doc_id such as brand, content or content_map, as a new version; the last 20 versions are kept. Pass base_version (the version you read, 0 when creating) so a concurrent edit is refused instead of overwritten. Nothing is published. Applies after interviewing the user about their brand, summarizing their top posts, or drafting a content map. 繁中：存品牌文件、內容文件或內容地圖，保留最近 20 版。

Input parameters:

- `account_id` (string): Optional connected account the document belongs to
- `base_version` (integer): Version you read; 0 when creating
- `content` (string, required): Whole document, Markdown or plain text, up to 50,000 characters
- `doc_id` (string, required): 1-40 chars of a-z, 0-9, _ or -; suggested: brand, content, content_map
- `language` (string): BCP 47 tag, e.g. zh-TW (default), en, ja
- `title` (string): Up to 100 characters

### `get_brand_doc` (~102 tokens)

Get a brand document

Returns one saved document by doc_id (latest, or an earlier version), or lists all documents when doc_id is omitted. Applies before generating or scheduling posts so the drafts follow the brand and content documents. 繁中：讀取品牌文件；不給 doc_id 就列出全部。

Input parameters:

- `doc_id` (string): Document id; omit to list all documents
- `version` (integer): An earlier version (the last 20 are kept)

### `analytics_insights` (~117 tokens)

Account insights

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.

Input parameters:

- `account_id` (string, required): Account id from list_accounts, or "all" for the organization-wide aggregate
- `period` (string): e.g. 7d, 30d (default 30d)

### `list_formulas` (~54 tokens)

List content formulas

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.

### `get_playbook` (~63 tokens)

Operating playbook

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.

### `connect_account_link` (~62 tokens)

Get a link to connect a new account

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.

### `disable_this_key` (~179 tokens)

Disable this connection

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.

### `get_my_usage` (~154 tokens)

My usage and call log

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.

Input parameters:

- `cursor` (string): next_cursor from the previous result
- `days` (integer): 1-30 (default 1 = today)
- `limit` (integer): 1-100 (default 50)

### `get_approval` (~134 tokens)

Check a confirmation request

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).

Input parameters:

- `id` (string, required): Approval id (apr_...) from error.approval_id

### `bulk_archive_library` (~69 tokens)

Archive library items in bulk

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.

Input parameters:

- `ids` (array, required): Item ids (max 50)

### `bulk_delete_library` (~61 tokens)

Delete library items in bulk

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.

Input parameters:

- `ids` (array, required): Item ids (max 50)

### `bulk_queue_library` (~78 tokens)

Queue library items in bulk

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.

Input parameters:

- `ids` (array, required): Draft ids (max 50)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ppcvote-mindthread/api-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 69
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 66

## Common questions

### What is the MindThread MCP server?

MindThread is an MCP server listed in the public MCP registry as io.github.ppcvote/mindthread. Threads scheduler for AI agents: write, schedule and publish posts, review replies, read insights. This page covers its hosted endpoint (https://mindthread.tw/api/mcp).

### Is the MindThread MCP server safe to use?

MindThread scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MindThread MCP server expose?

MindThread exposes 43 tools: get_me, list_accounts, get_material, build_material, get_account_settings, and 38 more. Their descriptions and schemas cost roughly 6,096 tokens of context every time the server is loaded.

### Does the MindThread MCP server require authentication?

No. We connected to MindThread without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MindThread MCP server still maintained?

MindThread is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mindthread.tw/api/mcp
- Repository: https://github.com/ppcvote/mindthread-mcp
- Website: https://mindthread.tw/developers
- Changelog RSS feed: https://verifymcp.io/servers/ppcvote-mindthread/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ppcvote-mindthread/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ppcvote-mindthread/api-mcp