{
  "markdown": "# mcp-bluesky\n\nBluesky MCP — wraps the AT Protocol API\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `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. |\n| `get_posts` | Fetch recent posts from a Bluesky user's timeline. Returns post text, timestamps, likes, reposts, reply counts, and threaded replies. |\n| `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. |\n| `get_feed` | Get posts from a Bluesky feed (e.g., \"discover\", \"what's-hot\"). Returns recent posts with authors, timestamps, and engagement counts. |\n| `get_followers` | Get a user's followers on Bluesky by handle. Returns follower profiles including handles, display names, bios, and follower counts. |\n| `get_follows` | Get accounts a Bluesky user follows by handle. Returns followed profiles with handles, display names, bios, and descriptions. |\n| `get_thread` | Fetch a post thread by URI. Returns the parent post and all replies in conversation order with timestamps, authors, and engagement data. |\n| `resolve_handle` | Convert a Bluesky handle to its DID (decentralized identifier). Returns the DID for programmatic account lookups. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"bluesky\": {\n      \"url\": \"https://gateway.pipeworx.io/bluesky/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/bluesky/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Bluesky data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3551,
  "sha": "43b5ceb986b658774b662a1acf7272c706bb8b44156bdba1fac8515be18f2dd7",
  "repo_slug": "pipeworx-io/mcp-bluesky",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_bluesky_9745554b/readme"
}