MCP server
Bluesky MCP server
Bluesky's AT Protocol is open, but Bluesky ships no official MCP server. Modiva hosts one with 8 typed tools, so an agent can post to Bluesky and read feeds and the firehose from the same server that runs its other networks.
Bluesky is the easiest network to build on and the least useful to build for in isolation: an agent that only posts to Bluesky is not much of an agent. Modiva's value here is unification: the same posts_create call that publishes to Instagram or LinkedIn also posts to Bluesky, so cross-posting is one tool call rather than one integration per network.
8 typed Bluesky tools
Grouped by resource, not by platform — so the same tool names work across every connected account.
accounts_
list · health · status
posts_
create · cross_post · schedule · publish_now
comments_
list · reply
messages_
list · send · inbox
analytics_
unified · best_time_to_post
Add it to your AI client
Point any MCP-compatible client (Claude, Cursor, Windsurf, …) at the hosted server and the Bluesky tools are discovered automatically.
{
"mcpServers": {
"modiva": {
"url": "https://mcp.modiva.ai/v1",
"headers": { "Authorization": "Bearer mk_live_…" }
}
}
}Connect Bluesky to your agent
Get your MCP key — freeFAQ
How does authentication work for Bluesky?
You connect your Bluesky account once in the Modiva dashboard and Modiva manages the session. The agent never sees credentials; it just calls tools.
Does Bluesky expose post analytics?
No. The AT Protocol currently has no analytics endpoint, so no tool can report Bluesky post performance. Likes and reposts are visible on the posts themselves.
Can the agent read feeds and the firehose?
Yes. Read tools cover your timeline, custom feeds and search, which is enough for an agent to monitor topics and join conversations.
Related
Modiva is a hosted, multi-tenant MCP server. Your Bluesky tokens are encrypted and never shared between workspaces.