Can I use Bluesky as a CLI?

Yes. KosmoKrator exposes a Bluesky CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Bluesky through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Bluesky tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Bluesky credentials stored?

Bluesky credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Bluesky MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

social

Bluesky MCP Integration for LangChain

Connect Bluesky to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 5 read 1 write Manual OAuth token auth

Submit Bluesky feedback View package source

Connect Bluesky to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Bluesky MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-bluesky": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=bluesky",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=bluesky --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Bluesky instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Bluesky Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Bluesky integration catalog.

MCP tool	Source function	Type	Description
`integration__bluesky__bluesky_create_post`	`bluesky.bluesky_create_post`	Write	Create a new post on Bluesky. The post text is required and supports facets (mentions, links, tags) if provided.
`integration__bluesky__bluesky_get_profile`	`bluesky.bluesky_get_profile`	Read	Get the public profile of a Bluesky user. Provide a handle (e.g. "alice.bsky.social") or DID.
`integration__bluesky__bluesky_list_followers`	`bluesky.bluesky_list_followers`	Read	List the followers of a Bluesky account. Returns follower profiles with handles, display names, and avatars.
`integration__bluesky__bluesky_list_following`	`bluesky.bluesky_list_following`	Read	List the accounts that a Bluesky user follows. Returns profiles with handles, display names, and avatars.
`integration__bluesky__bluesky_search_posts`	`bluesky.bluesky_search_posts`	Read	Search for posts on Bluesky. Supports full-text search queries. Returns matching posts with author, text, and timestamps.
`integration__bluesky__bluesky_get_current_user`	`bluesky.bluesky_get_current_user`	Read	Get the authenticated user's own Bluesky profile. No parameters required — uses the configured account.

Related Bluesky Pages

Bluesky CLIUse direct JSON commands instead of MCP discovery. Bluesky MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.