Threads MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADS_APP_ID | No | Meta app ID for OAuth only. | |
| THREADS_API_BASE | No | Threads Graph API base. Must be https://graph.threads.net/vX.Y. Default https://graph.threads.net/v1.0. | https://graph.threads.net/v1.0 |
| THREADS_MCP_VENV | No | Launcher virtualenv layout override. | |
| THREADS_APP_SECRET | No | Meta app secret for OAuth exchange only. Never store it in a file under version control. | |
| THREADS_GATE_PYTHON | No | Python interpreter for the gate and wrapper scripts, for example when the system python3 is older than 3.11. | |
| THREADS_LEDGER_PATH | No | Override for the publication ledger path. The launcher sets it from the XDG directories. | |
| THREADS_MCP_RUNTIME | No | Launcher layout override. | |
| THREADS_TOKEN_STORE | No | Override for the token store path. The launcher sets it from the XDG directories. | |
| THREADS_REDIRECT_URI | No | Meta app redirect URI for OAuth only. | |
| TOKEN_ENCRYPTION_KEY | No | Fernet key for the token store. Read from ~/.config/threads-mcp/encryption.key by the launcher. | |
| THREADS_GATE_REGISTRY | No | Gate registry path. | |
| THREADS_REQUEST_TIMEOUT | No | Seconds per request. Default 15. | 15 |
| THREADS_OAUTH_STATE_PATH | No | Override for the OAuth state path. The launcher sets it from the XDG directories. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Use this server to read the connected Threads account and publish content that has already been approved. Always supply a stable idempotency_key for publication. A result with status=unknown must never be blindly replayed. Read-only verification can help an operator, but an identical feed post cannot prove attribution.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| threads_get_profileA | Read the authenticated Threads profile. |
| threads_publish_textA | Publish one approved text post to Threads. idempotency_key must remain stable for retries of the same logical publication. Optional topic_tag (1-50 characters without '.' or '&'). Optional image_url (public HTTPS) turns the call into an image post, exactly like threads_publish_image. The tool prevents blind retries when provider outcome is unknown. |
| threads_publish_imageA | Publish one approved image post (text + public HTTPS image_url, optional topic_tag of 1-50 characters without '.' or '&') to Threads. idempotency_key must remain stable for retries of the same logical publication. The media container is published only after Threads reports it FINISHED. The tool prevents blind retries when provider outcome is unknown. |
| threads_get_postB | Fetch one Threads post by provider post id for verification. |
| threads_list_recent_postsB | List recent Threads posts for verification and duplicate detection. |
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 5 tools
Read tools (get_profile, get_post, list_recent_posts) and write tools are clearly separated by resource and action. The one blur is threads_publish_text vs threads_publish_image: publish_text explicitly becomes an image post when image_url is supplied, 'exactly like threads_publish_image', so an agent may be unsure which to call for image content.
Every tool uses the same threads_ prefix followed by a snake_case verb_noun pattern (get_profile, get_post, publish_text, publish_image, list_recent_posts). No mixing of conventions or vague verbs.
Five tools is well within the well-scoped range and each earns its place: two read/verification tools, two publish paths, and a recent-posts listing for duplicate detection. Nothing redundant or missing at the count level.
Core lifecycle of publish plus verify is covered, including idempotency and duplicate detection. However, there is no delete/retract, no reply or quote/repost capability, and no post-level insights/metrics, which are notable gaps for a Threads publishing surface.