Bluesky MCP integration for AI agents.
Connect AI agents to Bluesky through 4 structured actions, including get profile, create text post, and get timeline. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 4
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bluesky integration exposes
The Bluesky Agent App exposes 4 provider-backed actions for social and communication work. Its current contract lets an authorized agent get the detailed bluesky profile for a handle or did, create a bluesky text post in the authenticated account's repository, and get the authenticated account's home timeline with cursor pagination. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bluesky account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bluesky capabilities.
Showing 4 of 4 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_profileREADGet the detailed Bluesky profile for a handle or DID.
INPUTS: actor
create_text_postWRITECreate a Bluesky text post in the authenticated account's repository.
INPUTS: text / createdAt / langs / tags / facets
get_timelineREADGet the authenticated account's home timeline with cursor pagination.
INPUTS: algorithm / limit / cursor
search_postsREADSearch Bluesky posts with common filters and pagination.
INPUTS: q / sort / since / until / mentions
INPUT CONTRACTS
Know what the action needs before it runs.
get_profile
actorOPTIONAL- A Bluesky handle or DID.
create_text_post
textREQUIRED- The primary post text.
createdAtOPTIONAL- Client-declared timestamp for the post.
langsOPTIONAL- Human language codes for the post text.
tagsOPTIONAL- Additional hashtag values without the hash prefix.
facetsOPTIONAL- Rich text facets to attach to the post.
get_timeline
algorithmOPTIONAL- Optional Bluesky feed algorithm identifier.
limitOPTIONAL- The maximum number of posts to return.
cursorOPTIONAL- A cursor returned by Bluesky pagination.
search_posts
qREQUIRED- The Bluesky search query string.
sortOPTIONAL- The ranking order for matching posts.
sinceOPTIONAL- Return posts after this ISO date or datetime.
untilOPTIONAL- Return posts before this ISO date or datetime.
mentionsOPTIONAL- A Bluesky handle or DID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Profile
Get the detailed Bluesky profile for a handle or DID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_profileControl Create Text Post
Create a Bluesky text post in the authenticated account's repository. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_text_postVerify with Get Timeline
Get the authenticated account's home timeline with cursor pagination. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_timelineSAFETY BOUNDARY
Operate Bluesky with explicit limits
- Authorize Bluesky with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Bluesky rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Bluesky task completed successfully.
CONNECTION MODEL
API key
Bluesky app password used to create an AT Protocol session. Create an app password in Bluesky Settings > Privacy and Security > App Passwords: https://bsky.app/settings/app-passwords
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 3
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bluesky.