Threads MCP server

Also Meta's, but a separate app and a separate login -- so it gets its own connection.

Connect Threads All connectors

Tools: 7
Read-only: 5
Write: 2; Off by default
Destructive: 0; Flagged distinctly

What it does

Threads through an assistant

A small, focused connector: the connected account's profile, its posts, the replies underneath them, and per-post engagement -- views, likes, replies, reposts and quotes. Posting and replying are opt-in, so a connection can be read-only for as long as you want it to be.

Profile details for the connected Threads account
Your posts, and individual post lookup
Replies on any post
Per-post insights: views, likes, replies, reposts and quotes
Publish a post and reply to a thread (opt-in)

Ask your assistant

What people actually ask

Real questions, answered from live Threads data.

“Which of my last ten Threads posts got the most views?”

threads_list_poststhreads_get_post_insights

“What are people replying to under yesterday's post?”

threads_list_poststhreads_list_replies

“Pull the engagement numbers for the post I put out on Tuesday.”

threads_get_postthreads_get_post_insights

Tool catalogue

7 Threads tools

Grouped by what they touch. Every tool is individually toggleable — you expose only what you want.

All tools

7 tools5 read-only · 2 write

Showing 7 of 7 tools

threads_create_post
Write
Publish a text, image, or video post to the connected Threads account.
threads_get_post
Read-only
Get details of a single Threads post.
threads_get_post_insights
Read-only
Get engagement metrics (views, likes, replies, reposts, quotes) for a Threads post.
threads_get_profile
Read-only
Get the connected Threads account's profile (username, bio, profile picture).
threads_list_posts
Read-only
List recent posts from the connected Threads account.
threads_list_replies
Read-only
List replies to a Threads post.
threads_reply_to_post
Write
Post a reply to a Threads post.

Every tool name and description, machine-readable: /llms-full.txt

Access & safety

You decide what it can touch

The same model applies to every connector, and it defaults closed.

Authorize once

Connect Threads through its own consent screen. Credentials are encrypted with AES-256-GCM and never returned by any API response or tool call.

Writes off by default

A new connection switches on a read-oriented default set only. Every write tool must be enabled deliberately before any client can call it.

Roles enforced server-side

READ, WRITE and ADMIN gate tool invocation on the server, not just in the UI. A READ member's token is refused any write tool.

Setup

Connect Threads in minutes

No infrastructure to run. Copy one URL and one token into your client.

1Create a free workspace and connect Threads.
2Choose which tools to expose — writes stay off until you enable them.
3Copy your MCP endpoint URL and bearer token.
4Paste them into Claude, Cursor, or any MCP client.

claude_desktop_config.json

{
  "mcpServers": {
    "serve-mcp": {
      "url": "https://servemcp.com/api/mcp/your-workspace",
      "transport": "http",
      "headers": {
        "Authorization": "Bearer smcp_..."
      }
    }
  }
}