Threads for Claude

app.threads-mcpPublished by threads-mcp.appOfficial publisherv0.1.0Updated Oct 24, 2026

Publish, reply, moderate, search and read insights on your Threads (threads.com) account.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant publish, reply, moderate, search and read insights on a Threads (threads.com) account.

What you can do
This remote MCP server connects an assistant to a Threads account. According to its description, it can publish posts, reply to content, moderate activity, search, and read account insights. It is reached as a hosted endpoint rather than a local package.
When to use it
Worth adding when you want an assistant to handle Threads posting, replies, moderation, search, or performance insights directly from a conversation, instead of switching to the Threads app or site.
Requirements
A remote MCP endpoint at the provider's host, reached over streamable HTTP. Authentication is OAuth and is required, so you need a Threads account and must complete the provider's OAuth flow. No environment variables or headers are declared.
Before you install
The server can act on a live social account: publishing, replying, and moderating are visible, hard-to-undo actions, so review anything the assistant proposes before it runs. Access is granted through OAuth, so check which permissions the provider requests and revoke them when no longer needed. The provider is a third party and account content passes through it.

Installation

In SourceWeft

  1. Open Threads for Claude in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.threads-mcp%2Fthreads/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "threads-for-claude": {
      "type": "http",
      "url": "https://threads-mcp.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 30, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.