Bluesky
Read & post on Bluesky (the AT Protocol social network) from any AI agent. 9 tools, app-password auth.
7 天免费 · 无需信用卡 · EU 托管
问 Bluesky 任何事
通过 AnythingMCP 对 Bluesky 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 BlueskyClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Bluesky。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
Bluesky 指南
面向主流 AI 客户端的逐步设置。
配置 Bluesky
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector wraps the Bluesky AT Protocol XRPC API (bsky.social).
Setup:
- In the Bluesky app or web client → Settings → Privacy and Security → App Passwords → Add App Password.
- Name it (e.g. 'mcp') and copy the generated
xxxx-xxxx-xxxx-xxxxpassword. App passwords scope down what they can do — never use your account password. - Set
BLUESKY_HANDLE(e.g.you.bsky.social) andBLUESKY_APP_PASSWORD.
Two-step auth: AT Protocol uses a session model. You can't just send the app password on every call — you must first POST to /xrpc/com.atproto.server.createSession with {identifier, password} and use the returned accessJwt as the Bearer token. The bluesky_create_session tool does step 1; subsequent tools use the JWT.
For production use the access JWT should be cached (it lasts ~2 hours) and refreshed with refreshJwt via /xrpc/com.atproto.server.refreshSession. This adapter exposes session create + refresh as tools so the caller can manage lifecycle.
DIDs vs handles: Bluesky internally uses DIDs (did:plc:abcd...). Public APIs accept either DID or handle (you.bsky.social); use bluesky_resolve_handle to convert.
Post records: posts are AT Protocol records of type app.bsky.feed.post. They have text (max 300 graphemes), createdAt (RFC3339), langs[], and optional embed for images/links.
Rate limits: 5k req / hour per JWT; create-session limited to 30/5min per IP. 429 with Retry-After.
Out of scope here: image upload multipart (use the public URL embed pattern instead), labelers/moderation, custom feeds CRUD, DM (separate API), the firehose.