A social networking service designed as a decentralized alternative to Twitter, built on the AT Protocol for a more open social media ecosystem
Why this server?
Enables retrieval of Bluesky posts from a Metricool account for analysis and metrics tracking.
Why this server?
Enables cross-posting content to Bluesky alongside X and LinkedIn: tweets and threads created via create_tweet/create_thread accept a platforms array (e.g. ["x","bluesky","linkedin"]) to publish the same content to Bluesky in one call, with per-network results showing what published, failed, or was skipped, and platform status reporting for connected/usable Bluesky accounts.
Why this server?
Allows AI agents to manage Bluesky content through PostSider, including creating drafts, scheduling posts, requesting approvals, uploading media, and reading analytics.
Why this server?
Includes a site extractor to fetch and extract readable content from Bluesky URLs as markdown.
Why this server?
Draft Bluesky post drafts for social content and community updates.
Why this server?
Allows managing Bluesky accounts through PlanVortex, including scheduling posts and interacting with mentions and comments.
Why this server?
Connects to Bluesky/ATProtocol APIs, enabling interaction with Bluesky features such as fetching and analyzing feeds and followers, accessing timeline posts, searching content, managing posts (reading, creating, liking), and following users through natural language commands.
Why this server?
Allows posting to Bluesky, scheduling posts, checking per-platform results, retrying failed publishes, and managing draft/publish workflows.
Why this server?
Allows publishing and scheduling content to Bluesky social accounts, including post creation, scheduling, and analytics.
