Skip to main content
Glama
521,191 tools. Updated 2026-09-06 10:36

"Threads" matching MCP tools:

  • Schedule multiple posts at once from CSV content. USE THIS WHEN: • User has a spreadsheet or list of posts to schedule • Planning a content calendar for a month • Migrating content from another tool CSV FORMAT (required columns): • platform: linkedin, instagram, x, tiktok, threads • scheduled_time: ISO 8601 format (e.g., 2024-02-15T10:00:00Z) • text: Post content/caption OPTIONAL COLUMNS: • media_url: Image or video URL • first_comment: First comment to add (Instagram/LinkedIn) • hashtags: Additional hashtags to append PROCESS: 1. First call with validate_only: true to check for errors 2. Review validation report with user 3. Call again with validate_only: false to execute import
    ConnectorNo auth
  • Set the caller's inbox_mode + (for 'quiet') inbox_quiet_min_karma. Mirrors ``PATCH /me/inbox``. The recipient-side opt-out for cold DMs — the natural counterpart to ``colony_get_cold_budget`` which tells you your sending budget. Modes: * ``open`` (default) — accept cold DMs from any sender past the platform floor. * ``contacts_only`` — accept only warm threads + peers you have messaged first. * ``quiet`` — accept only from senders whose karma clears ``inbox_quiet_min_karma``. The threshold is REQUIRED when mode is ``quiet`` and is cleared to NULL when mode flips to anything else (a stale value would confuse the receiver opt-out logic in Phase 3). Stored Phase 1; enforced in Phase 3 (THECOLONYC-106). Idempotent — posting the same mode twice is a no-op. Response shape mirrors the REST endpoint: { "inbox_mode": "quiet", "inbox_quiet_min_karma": 5 }
    ConnectorNo auth
  • Pick which connected channels to post to. **Call this before publish and show the result to the person.** Leave scope empty to get the candidate list and let them choose. Use scope: "all" for every active channel, or an array mixing platform names ("threads"), handles ("@vibe.trender") and account ids. Duplicates are folded, expired and not-yet-live channels are dropped into `skipped` with a reason, a sentence you can read to the person, and a link to reconnect. Pass the returned accountIds to publish unchanged. `limits` is the tightest rule across the chosen channels, so write to that. If both accountIds and candidates come back empty, nothing is connected yet. Send the person to https://uplika.com/dashboard/connections to connect a channel, then call this again.
    ConnectorNo auth
  • Sends a reply to the customer on an existing ticket and DELIVERS it immediately (customer email plus any connected chat threads). This is not a draft and it reaches the customer. Use this once you have a final, customer-ready answer; to instead queue a reply for human approval, use the draft tool. Requires a "send"-tier credential (a draft-tier credential is refused) and the ticket must already have a customer email on file or the call is rejected. [$0.06 draft / live when trusted]
    ConnectorNo auth
  • Surface known UNRESOLVED problems matching a free-text description: forum threads with zero replies but high views, plus open GitHub issues. Answers "is anyone else hitting this?". Canton-specific. Does NOT return fixes, solutions, config, or how-to steps, and returns nothing when no open issue matches; for "how do I fix / configure / why does X happen" use semantic_search (then get_doc) instead.
    ConnectorNo auth
  • Search a single network for posts matching a query, returned as the unified Post[] schema and tagged with its platform. Keyless on TikTok, YouTube, and Pinterest. Instagram, Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set). Snapchat and Threads do not support keyless search (returns not_supported); LinkedIn is quarantined. To fan one query across every network at once, use search_all.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Provides read-only access to public Threads.net profiles and threads via anonymous scraping, with tools for profile info, user threads, and session management.
    3
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    An MCP server for Meta's Threads that acts as your own account, enabling reading profiles, posts, replies, timeline, search, and performing actions like posting, replying, liking, following, and scheduling, using a real logged-in browser session.
    24
    25
    MIT

Matching MCP Connectors

  • Plan, draft, schedule and publish social posts grounded in a stored Website Brain — the product context Cadencz builds by reading your site once, so drafts start from what you actually built instead of a prompt. 16 tools covering platform-native composing across 9 channels (LinkedIn, X, Bluesky, Threads, Mastodon, Telegram, Discord, Slack, dev.to), weekly planning, scheduling and analytics. Nothing publishes without human approval.

  • Connect Claude or any MCP client to Thread Otter, a GTM agent for founders. Free tools with no key: find_buyer_threads (give it a website URL and get recent Reddit threads where that product's buyers are asking for it, report in ~3 minutes), reddit_demand_board (weekly demand across 40 communities with thread receipts), and subreddit_rules (promotion posture for 2,000+ profiled subreddits). With an API key: read your buying-intent mentions across Reddit, X, LinkedIn, and Bluesky, check your pipeline, and propose posts and reply drafts in your voice. Propose-only by design: nothing sends without your approval flow. Keys at threadotter.com/connect.

  • List artifacts this principal owns, newest-updated first; account-visible artifacts owned by others are intentionally excluded. Returns metadata and lifecycle counts without loading source. Use get_document for one artifact’s versions, reviews, threads, or source.
    ConnectorOAuth
  • Read one viewable artifact’s metadata, versions, visible review requests, threads, and optional source without changing state. Source defaults to the latest version unless versionId selects another; includeSource defaults to true. Embedded image bytes are omitted, so use the version resource when complete source is required.
    ConnectorOAuth
  • Check a post against every major platform's length limit at once. FREE. Covers X, LinkedIn posts and headlines, Instagram captions, Threads, YouTube titles, and meta descriptions. Typical input {"text": "<post>"} returns {"chars": N, "platforms": {"x_post": {"limit": 280, "fits": true, "over_by": 0}, ...}}. Use before posting, to catch truncation. Not for readability (analyze_writing) and not for reading duration (reading_time). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Fetch a single web page and extract clean content. Auto-tier server-side: handles SSR (Next.js, Nuxt, TikTok, Pinterest, YouTube), SPA shells, PDFs, paywall detection, residential-proxy escalation, and stealth profiles for TikTok / Instagram / Pinterest / YouTube. Returns clean markdown (default) with a YAML frontmatter header (url, outcome, total_chars). Read 'outcome' to classify the result (success | teaser | thin_content | paywall | bot_challenge | consent_wall | login_wall | rate_limited | timeout | transient_upstream | unsupported_target | not_found | error). Large pages (>80k chars) are truncated inline with truncated_chars + a download_full_url to the complete extraction (expires ~1h). Permanently unsupported (outcome=unsupported_target, cost=0 upstream): Bluesky search, Instagram post/reel and tag/explore pages (profiles work), Pinterest search, g2.com, Truth Social, Xiaohongshu. Threads and Instagram profile pages ARE supported.
    ConnectorNo auth
  • Submit manual content to a pipeline for transformation. Use when user says "add this to my changelog", "create a newsletter from this", "transform this content", or provides content to be processed. Content will be transformed using the pipeline's persona and ICPs. Social pipelines publish to the pipeline's declared destination (x/linkedin/instagram/facebook/threads — set via update_pipeline; undeclared defaults to x) after human approval; instagram items REQUIRE media_artifact_ids. [write-tier — first use may require a manager's approval; a from-now-on approval makes future calls seamless, a just-once approval re-asks next time.]
    ConnectorNo auth
  • Retrieve Infrastructure Threads — the factual material-link layer recording where the same named AI hardware asset (chip / GPU / NPU / custom ASIC) appears as a documented fact in two events. A thread is not a Coordination Connection: no connection type, no confidence grade — either the asset match is verified or it isn't. Pass `event_id` for that event's linked events in both directions: outbound = assets this event deploys or trains on, each linking to its producer event; inbound = events that use this event's asset. Each link carries the sourced claim (`linkType` ∈ deploys | trains_on | powered_by | fabricated_at, plus the asset) and the host-event field that names it. Omit `event_id` for the whole layer. For one event's value-chain stack, use `get_event_stack`. Free on both tiers.
    ConnectorNo auth
  • [chieflab_* alias of chiefmo_publish_approved_post] Publish an approved social post (LinkedIn / X / Threads / Instagram / Facebook / Bluesky / TikTok) through the social publishing rail (current adapter: zernio). USE WHEN the user has approved a publishAction from chiefmo_launch_product on the reviewUrl and you need to fire the post. Strict approval gate: returns { reason: 'requires_approval', reviewUrl } if the action isn't approved yet. Once executed, returns the live platform post URL. Money/external-system action — never call this without an approved actionId.
    ConnectorNo auth
  • Read messages from a consultation thread (own thread for responders; any thread for askers). WHEN TO USE - Before replying to a consultation thread — check the full history first. - To retrieve a scope_proposal's deliverable_type and metadata before sending scope_accepted. - To check if an extension_request was accepted. WHEN NOT TO USE - For full consultation content (question, responses) — use get_consultation. BEHAVIOR - Read-only. Auth required. Rate-limited to 60 req/min. - Visibility: askers see all threads on their consultation; responders see only their own thread. - Returns messages in chronological order (oldest first) with kind, body, metadata, from_agent_id, created_at. WORKFLOW - Responders: call read_messages before send_message to avoid duplicate proposals. - Askers: call read_messages with responder_agent_id to check a specific thread before sending scope_accepted.
    ConnectorNo auth
  • List comments in a workspace. Filter by `target_type` (row, cell, doc_range, html_element, surface, workspace), `target_id`, `surface` (returns every comment anchored to any element of one surface, useful for 'open threads on this tab'), `status` (open | resolved | all, default open), `mentioning_me: true` for comments that @-mention the caller, or `author: <principalId>` for comments by a specific user/agent. Returns up to 200 comments per call ordered by `createdAt` asc, with `surfaceSlug` denormalized for doc_range/html_element/surface targets so reply paths work even across archive boundaries. Use `get_comment_thread` to pull a single comment plus its replies + reactions.
    ConnectorNo auth
  • Community-discourse search via parallel.ai with optional platform filtering. Returns synthesized text excerpts plus direct URLs to real Reddit threads, X posts from named operators, Substack essays, LinkedIn posts, Facebook posts. Use for: "what are practitioners saying about X", recurring themes in founder voice, multi-platform discourse mapping, verbatim quotes from named individuals. Per Phase 3.5 empirical A/B (Docs/solutions/architecture-decisions/search-backend-architecture-jun04.md): this tool SOLVES the Reddit/X retrieval gap that perplexity_search fundamentally couldn't fill. Optional platforms[] to restrict (e.g. ["reddit","x","substack"]). Per social-listening-synthesis §3 sample ≥3 platforms per brief.
    ConnectorNo auth
  • Mark a 1:1 DM conversation as spam — **1:1 only** (group threads are not addressable through this tool), **reversible** (call ``colony_unmark_conversation_spam`` to clear), **reports the other user** in the conversation, and **routes to platform admins**, not per-colony moderators (private DMs are outside colony mods' remit). Effects: the conversation is hidden from your inbox and a ``DmSpamReport`` is queued for platform-admin review. Idempotent — re-marking a conversation you already have a pending report on is a no-op (returns ``replayed: true``) without inserting a duplicate audit row. Returns an envelope with ``conversation_id``, ``spam_reported_at``, ``spam_reason_code``, ``report_id``, and ``replayed`` so the caller can distinguish first-mark from idempotent re-mark without parsing the message text.
    ConnectorNo auth
  • List the group DM conversations you're a member of, newest activity first. Each entry includes the group ``conversation_id`` (use it with ``colony_get_group_conversation`` / ``colony_send_group_message``), title, creator, member count, last-message timestamp, and your unread count. Returns groups only — pair-DM threads come back through ``colony_list_conversations``. Requires authentication.
    ConnectorNo auth
  • Set the caller's inbox_mode + (for 'quiet') inbox_quiet_min_karma. Mirrors ``PATCH /me/inbox``. The recipient-side opt-out for cold DMs — the natural counterpart to ``colony_get_cold_budget`` which tells you your sending budget. Modes: * ``open`` (default) — accept cold DMs from any sender past the platform floor. * ``contacts_only`` — accept only warm threads + peers you have messaged first. * ``quiet`` — accept only from senders whose karma clears ``inbox_quiet_min_karma``. The threshold is REQUIRED when mode is ``quiet`` and is cleared to NULL when mode flips to anything else (a stale value would confuse the receiver opt-out logic in Phase 3). Stored Phase 1; enforced in Phase 3 (THECOLONYC-106). Idempotent — posting the same mode twice is a no-op. Response shape mirrors the REST endpoint: { "inbox_mode": "quiet", "inbox_quiet_min_karma": 5 }
    ConnectorNo auth
  • Get a Bluesky user's recent feed ordered newest-first. Every filter includes reposts, so items authored by other accounts appear alongside the actor's own writing — a "repostedBy" field marks those, and the "author" field always names who actually wrote the post. Filter by post type: "posts_with_replies" (everything), "posts_no_replies" (excludes replies), "posts_with_media" (posts with images or links), or "posts_and_author_threads" (posts the author started). Returns posts with full text, engagement counts, embeds, and AT-URIs for drilling into threads via bsky_get_post_thread. Because "limit" counts reposts too, a page from an account that reposts heavily holds far fewer of that account's own posts than the limit suggests; the enrichment fields report the split, so read "originalPosts" rather than the limit when you want the actor's own writing. Supports cursor pagination.
    ConnectorNo auth
  • Unified reply inbox across mailboxes. Cursor-paginated → { threads[], nextCursor }; each row: threadId, campaignName, leadEmail, subject, mailboxEmail, label, lastEventType, markStatus. Filters: mailbox, campaign, label, read, includeNonreply (bounces/OOO, default true), archived (exclude|include|only). Use thread for one thread's history.
    ConnectorNo auth