Bluesky Posts Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, available from console.apify.com/account/integrations. The server can list its tool without a token, but calling the tool requires one. |
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_bluesky_postsA | Search public Bluesky posts by keyword, read an account's posts, or read a post and its replies. Returns exact like, reply, repost, and quote counts, dates, hashtags, links, and images. No login. 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
Only one tool exists, so there is nothing to confuse it with. The description clearly defines its three modes: keyword search, account feed reading, and post plus replies retrieval.
get_bluesky_posts follows a clear verb_noun convention and is readable, though 'get' combined with a plural noun covers multiple read modes, which is slightly imprecise but harmless for a single tool.
A single tool that multiplexes three distinct operations—search, account timeline, and thread reading—is too thin for the stated purpose. Separate tools per mode would make the surface clearer.
Reading posts, replies, and search are covered, which matches the scraper's read-only domain, so no create/update/delete gap applies. However, no paging or filtering controls are exposed, and bundling three operations into one tool leaves notable gaps in usability.