Bluesky
Connect Bluesky to read your timeline and notifications, search, post and reply, follow people, and handle your direct messages.
Nothing has to be typed into PopMCP. You click Authorize with Bluesky, sign in to Bluesky and approve PopMCP. There is no developer app, callback URL or approval to wait for. Under More options you can connect with your handle and an app password instead of signing in, made in Bluesky under Settings, Privacy and security, App passwords. Never your main password.
- Setup time
- 1 min
- Auth
- OAuth authorization
- API base URL
- https://bsky.social/xrpc
Before you begin
- A Bluesky account. Any plan: Bluesky has no paid tier for its API
- Pop-up blockers must allow the Bluesky sign-in window to open
- Only if the AI should post or change anything: an owner or admin in PopMCP to allow write actions
Get your credentials
Start the connection from PopMCP
Open the Bluesky connector in PopMCP and click Authorize with Bluesky. There are no fields to fill in: no API key, no developer app and nothing to register. If your account is hosted outside Bluesky, type your handle under More options first.
Sign in to Bluesky and approve
The sign-in window opens on bsky.social. Sign in with the account the AI should work with, then approve PopMCP. Bluesky lists what is being asked for: posting and reading on your behalf, and your direct messages. PopMCP never sees your password.
Sign in to Bluesky
PopMCP is asking to use your Bluesky account.
This page belongs to Bluesky. You approve PopMCP on the next screen, and you can remove its access later from your Bluesky account.
Or use an app password
Optional, instead of signing in. In Bluesky open Settings, Privacy and security, App passwords, then Add App Password. Give it a name of at least 4 characters. Tick Allow access to your direct messages if the AI should read or send them. Click Next, then Copy App Password: Bluesky shows it only once. In PopMCP paste it with your handle under More options.
Add App Password
Please enter a unique name for this app password or use our randomly generated one.
An app password looks like abcd-efgh-ijkl-mnop. PopMCP refuses anything else, so your main password can never be used by mistake.
Check it is connected
The Bluesky card in PopMCP reads Connected, with your handle. New connections start read-only: the AI can read your timeline, notifications and direct messages, and posting waits until an owner or admin allows write actions in PopMCP.
Bluesky
- Status
- Connected
- Account
- @alice.bsky.social
- Access
- Read only
Connect in PopMCP
Open your workspace, choose Bluesky in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| How you connectpreset | Click Authorize, sign in to Bluesky and approve. There is nothing to copy or paste, and PopMCP never sees your password. |
| Your handletext | Only needed with an app password, or when your account is hosted outside Bluesky. |
| App passwordsecret | To connect without signing in. Make one in Bluesky under Settings, Privacy and security, App passwords. Tick direct messages access if your AI should read or send them. Never your main password.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Bluesky immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Permissions PopMCP requests
These are the scopes sent to Bluesky at authorization time.
| Scope | Why PopMCP asks for it |
|---|---|
| atproto | Required on every Bluesky sign-in. It names your account to PopMCP. |
| transition:generic | Read and write your posts, likes, follows, lists, preferences and files. It does not reach your email, password or account settings. |
| transition:chat.bsky | Read and send your direct messages. |
Verify it worked
The Bluesky card in PopMCP shows Connected with your handle. Asking the AI for the connection profile (bluesky_connection_profile) names the account, and asking how the account is doing (bluesky_account_summary) returns your follower count and recent posts rather than an authorization error.
Troubleshooting
The sign-in window never opens
Why: A pop-up blocker is stopping the Bluesky sign-in window.
Fix: Allow pop-ups for PopMCP in your browser and click Authorize with Bluesky again.
"That is not an app password"
Why: The value is not in the form abcd-efgh-ijkl-mnop. It may be your main password, which PopMCP never accepts.
Fix: Make an app password in Bluesky under Settings, Privacy and security, App passwords, and paste that.
"Bluesky did not accept that handle and app password"
Why: The handle has a typo, the password was copied in part, or it was deleted.
Fix: Check the handle, including the part after the dot. Bluesky shows an app password only once, so if in doubt add a new one.
"Bluesky limits how often an account can log in"
Why: Too many logins with an app password in a short time.
Fix: Wait for the time the message gives, then connect again. Once connected, PopMCP renews the session without logging in again.
"Bluesky sign-in needs a public web address"
Why: PopMCP is running on a local address, which Bluesky cannot reach to check who is asking.
Fix: Connect with an app password under More options.
"Direct messages need extra permission"
Why: An app password made without direct message access.
Fix: Add a new app password with Allow access to your direct messages ticked, then reconnect Bluesky with it.
"Your Bluesky sign-in has ended"
Why: The sign-in went unused for six months, or PopMCP's access was removed in Bluesky.
Fix: Reconnect Bluesky in PopMCP: one click on Authorize with Bluesky.