Who is this person
A name comes up in a sales call. Memtro already knows @dana.bsky.social quoted the account's launch post on 14 October saying it solved a problem she had, because the hourly sync recorded it.
What people say to and about your Bluesky account, remembered every hour.
Connect a Bluesky account with its handle and an app password and Memtro reads its profile and follower counts, its posts with likes and replies, notifications, threads and search results. Every hour the sync writes each mention, reply and quote of the account into memory. When you ask, and once an administrator has granted the action by name, it can publish a post or reply, like, repost, follow, block or mute accounts, and delete its own posts. Posts, likes, reposts, follows and blocks are public as the account, and a deleted post is gone for good.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Bluesky tool, reads what it needs, and answers with the source cited.
These tools change something in Bluesky. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Bluesky is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
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
A name comes up in a sales call. Memtro already knows @dana.bsky.social quoted the account's launch post on 14 October saying it solved a problem she had, because the hourly sync recorded it.
Zoe Clarke, marketing lead at Acme, asks what came in overnight. Memtro lists two replies asking about pricing, drafts an answer and reads it back. When Zoe approves, it publishes the reply beneath the question as the account.
The teams that lean on Bluesky most, a question each of them asks, and what they connect beside it.
A record in Bluesky is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Bluesky go to Settings → Privacy and security → App passwords → Add App Password, name it (Memtro, say) and copy the password shown: it is shown once
Leave 'Allow access to your direct messages' off. Memtro does not read them
In Memtro open Connections → Bluesky, paste the account's Handle and the App password, and connect. An account on another PDS also needs that server's PDS URL
Ask who mentioned you this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Bluesky tools are the same everywhere.
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. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Bluesky records into memory as entities.
Handle and app password. In Bluesky go to Settings → Privacy and security → App passwords → Add App Password, name it (Memtro, say) and copy the password shown: it is shown once.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time