MCP.so
Sign In

bluesky-daily-mcp

@briangershon

About bluesky-daily-mcp

An MCP Server to help you surface the most interesting topics from your Bluesky follows daily.

Basic information

Category

Other

License

MIT

Runtime

node

Transports

stdio

Publisher

briangershon

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is bluesky-daily-mcp?

bluesky-daily-mcp is an MCP server that retrieves all posts from your Bluesky follows for a given day, making it easy for an LLM to surface the most interesting topics. It caches posts and provides sample prompts for analysis.

How to use bluesky-daily-mcp?

Configure it in your MCP client (e.g., Claude Desktop) by adding the server to claude_desktop_config.json with required environment variables (BLUESKY_HANDLE, BLUESKY_APP_PASSWORD, TIMEZONE_OFFSET). After restarting the client, you can type prompts like “Retrieve Bluesky posts from yesterday” or “Retrieve Bluesky posts from April 2nd”.

Key features of bluesky-daily-mcp

  • Retrieves all posts from your Bluesky follows for any day.
  • Caches retrieved posts for efficient reuse.
  • Combines author and post fields for easy LLM consumption.
  • Uses bsky-tldr to shave down data and limit API calls.
  • Configurable timezone offset to define “day.”
  • Adjustable request timeout to handle large feeds.

Use cases of bluesky-daily-mcp

  • Daily feed summary and trend analysis from followed Bluesky users.
  • Discovering popular topics and discussions among your follows.
  • Feeding curated post data into an LLM for personalized insights.
  • Comparing content across different days to spot shifts in interest.

FAQ from bluesky-daily-mcp

How do I get started?

Install bluesky-daily-mcp via your MCP client (e.g., Claude Desktop) using the provided JSON configuration. You need a Bluesky account with an app password and a timezone offset.

What environment variables are required?

You must set BLUESKY_HANDLE (your handle without @), BLUESKY_APP_PASSWORD (from Bluesky settings), and TIMEZONE_OFFSET (e.g., -8 for PST). Optionally set REQUEST_TIMEOUT_MS (default ~60s, recommend 120000 for large feeds).

What are the limitations of bluesky-daily-mcp?

Retrieving all posts from your follows for a day can produce a large feed, leading to truncation by the MCP client or LLM context window. Additionally, retrieving historic dates (weeks/months ago) may hit Bluesky API rate limits or timeouts.

How does the timezone offset work?

The TIMEZONE_OFFSET (in hours from UTC) defines what “day” means for you. It ensures posts are retrieved only within that day’s window, not hard‑coded to UTC.

Can I run bluesky-daily-mcp locally?

Yes, you can clone the repository, run npm install && npm run build, and configure your MCP client to point to the built dist/index.js. Use the provided .env file for local development and debugging.

Comments

More Other MCP servers