threads-growth-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THREADS_USER_ID | Yes | Your Threads user ID | |
| THREADS_ACCESS_TOKEN | Yes | Your Threads API access token from Meta Developer App |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_to_threadsB | Threads pe naya text post publish karo |
| reply_to_threadC | Kisi thread/post ka reply karo |
| get_my_threadsB | Apne recent Threads posts dekho |
| get_my_profileA | Apni Threads profile info dekho (username, bio, followers) |
| get_thread_insightsA | Kisi thread ke insights dekho (views, likes, replies) |
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
Each tool targets a distinct operation: profile viewing, listing posts, insights retrieval, posting, and replying. No functional overlap.
All tools use a consistent verb_noun pattern with underscores (get_my_profile, get_my_threads, get_thread_insights, post_to_threads, reply_to_thread).
5 tools is well-scoped for a Threads growth server, covering essential read/write operations without bloat.
Covers core functionality (read profile, list posts, get insights, post, reply). Minor gaps like deleting posts or viewing other users are acceptable for a focused growth server.