Multi Platform Social Posts and Comments MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call needs one to start the Apify actor run. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_social_posts_commentsA | Search public posts and comments on Bluesky, Hacker News, Mastodon, Lemmy, Reddit, and YouTube, or read the comments on given post addresses. Returns one row layout across platforms. No login. Instagram, X, Facebook, TikTok, and LinkedIn are not covered. Pay per event on Apify. |
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 1 tool
There is only one tool, so an agent cannot misselect between competing tools. The description clearly states the two supported modes: searching public posts/comments or reading comments on given post addresses.
The single tool uses a clear snake_case verb_noun-style name. With only one tool there is no inconsistent pattern, though the compound 'social_posts_comments' is slightly less clean than a simpler verb_object name.
A one-tool surface feels thin for a server covering six platforms and two distinct modes: search versus comment retrieval on specific posts. It is functional but borderline under-scoped rather than clearly well-scoped.
The tool covers the core read-only domain: searching public posts/comments across several platforms and reading comments for given post addresses. Minor gaps remain, such as dedicated post-detail or author/profile retrieval, but the main stated workflows are represented.