Bluesky MCP server
Bluesky in any MCP client, through Memtro: Bluesky does not publish this server. Memtro's Bluesky connector reads Bluesky through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Bluesky: the account's profile and follower counts, its posts with likes, reposts and replies, notifications (mentions, replies, likes, new followers, unread count), search across all of Bluesky, and any post's thread; when you ask it can also post or reply, like or repost a post, follow, block or mute an account, and delete the account's own posts, likes, reposts, follows and blocks.
Reads
bluesky_profileA Bluesky profile: display name, bio, followers, follows, post count, when the account was made and its link.bluesky_postsPosts by an account, newest first (default: the connected account's own), each with text, time, likes, reposts, replies and quotes…bluesky_notificationsThe connected account's notifications, newest first, plus the unread count: who liked, reposted, replied to, quoted or mentioned it and when…bluesky_search_postsSearch posts across Bluesky: words or a phrase (Lucene-style syntax), newest first or by relevance ("top"), optionally by author…bluesky_threadA post and its conversation, from its at:// URI or bsky.app link: the posts above it (what it replied to, oldest first), the post itself…
Acts, when you ask
These change something in Bluesky. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
bluesky_postPublishes a post on Bluesky as the connected account, public and immediate, or a reply beneath an existing post when reply_to is given.bluesky_like_postLikes a Bluesky post as the connected account.bluesky_repostReposts a Bluesky post as the connected account, so it appears in the account's feed to all its followers.bluesky_follow_accountFollows a Bluesky account as the connected account.bluesky_block_accountBlocks a Bluesky account for the connected account: neither can see or reply to the other's posts.bluesky_mute_accountMutes or unmutes a Bluesky account for the connected account, so its posts stop (or start again) appearing in the account's feeds and notifications.bluesky_delete_recordDeletes one of the connected account's own Bluesky records: a post (it disappears for everyone, permanently), or a like, repost, follow or block…
Connect it
First connect Bluesky on Dashboard → Connections, then add Memtro to your client once. The Bluesky tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Bluesky connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Who mentioned or replied to us on Bluesky this week, and what did they say?
- › How many followers do we have now, and how did our last ten posts do?
- › What are people saying about 'company memory' on Bluesky this month?
- › Show me the whole thread under our launch post
- › Reply to Sam's question under the launch post with the pricing link
Questions
- Is this an official Bluesky MCP server?
- No. It is Memtro's MCP server with Memtro's Bluesky connector behind it: the connector reads Bluesky through its API with the credentials you connect on Dashboard → Connections, and Bluesky publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Bluesky?
- Only when you ask, and only what it has been granted: publish a post, or a reply to a post, as the connected account; like a post (the author is notified); repost a post to the account's followers (the author is notified); follow an account (it is notified); block an account (a public record); mute or unmute an account (private); delete one of the account's own posts, likes, reposts, follows or blocks. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.