Uluesky

Bluesky MCP — wraps the AT Protocol API

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "uluesky": {
      "command": "npx",
      "args": [
        "-y",
        "uluesky"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

mcp-bluesky

Bluesky MCP — wraps the AT Protocol API

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool	Description
`get_profile`	Look up a Bluesky user's profile by handle (e.g., "alice.bsky.social"). Returns display name, bio, follower/following counts, avatar, and verification status.
`get_posts`	Fetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies.
`search_posts`	Search Bluesky posts by keyword or phrase. Returns matching posts with author handles, timestamps, engagement metrics, and content.Requires bsky_handle and bsky_app_password in the gateway URL query params.
`get_feed`	Get posts from a Bluesky feed (e.g., "discover", "what's-hot"). Returns recent posts with authors, timestamps, and engagement counts.
`get_followers`	Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts.
`get_follows`	Get accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions.
`get_thread`	Fetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data.
`resolve_handle`	Convert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

config.json

{
  "mcpServers": {
    "bluesky": {
      "url": "https://gateway.pipeworx.io/bluesky/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/bluesky/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

config.json

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

Code

ask_pipeworx({ question: "your question about Bluesky data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Social Media View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Uluesky

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "uluesky": { "command": "npx", "args": ["-y", "uluesky"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/uluesky?style=directory)](https://allmcps.com/mcp/uluesky)

HTML Embed

<a href="https://allmcps.com/mcp/uluesky"><img src="https://allmcps.com/api/badge/uluesky?style=directory" alt="Uluesky on AllMCPs" /></a>

Technical Specs & Signals

CategorySocial Media

24Quality signal: Emerging · 24/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools9/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🌐 Social Media →Best MCP servers for Social Media →Alternatives to Uluesky →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

mcp-bluesky

Bluesky MCP — wraps the AT Protocol API

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool	Description
`get_profile`	Look up a Bluesky user's profile by handle (e.g., "alice.bsky.social"). Returns display name, bio, follower/following counts, avatar, and verification status.
`get_posts`	Fetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies.
`search_posts`	Search Bluesky posts by keyword or phrase. Returns matching posts with author handles, timestamps, engagement metrics, and content.Requires bsky_handle and bsky_app_password in the gateway URL query params.
`get_feed`	Get posts from a Bluesky feed (e.g., "discover", "what's-hot"). Returns recent posts with authors, timestamps, and engagement counts.
`get_followers`	Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts.
`get_follows`	Get accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions.
`get_thread`	Fetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data.
`resolve_handle`	Convert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

config.json

{
  "mcpServers": {
    "bluesky": {
      "url": "https://gateway.pipeworx.io/bluesky/mcp"
    }
  }
}

What this endpoint actually serves

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

config.json

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

Code

ask_pipeworx({ question: "your question about Bluesky data" })

The gateway picks the right tool and fills the arguments automatically.

License

MIT