Muridian is an MCP server. It gives an AI assistant you already use three things it does not have on its own: the ability to publish and schedule to X, to search and read public posts across four networks, and a workspace that remembers what you found and how it performed.
Getting started
- Create an account at muridian.xyz and paste your website. We read the page for your name and a description, you correct whatever is wrong, and that is the whole of onboarding. Nothing else is inferred from your site, and it is only ever read when you ask.
- Connect X from Settings. Nothing can be published until you do. Stripe, Search Console, Vercel and Supabase are optional and read-only.
- Connect your assistant. Settings has a one-click link for Claude, and the MCP endpoint URL for any other client that speaks the protocol.
Connecting an AI assistant
Muridian is an OAuth 2.1 authorization server. Your client registers itself, sends you to a consent screen listing exactly what it is asking for, and receives a token scoped to what you approved.
Six permissions exist, and a client only ever gets the ones you approve. Reading public posts, publishing as you, and your private workspace are three separate decisions — someone evaluating a new client has a real reason to grant the first without the second. The three business permissions are separate again, because revenue is a different disclosure from a search result.
Every connected app is listed in Settings with when it was last used, and disconnecting is immediate.
What it can do
- Know your company. One editable page — what you do, who it is for, what you are working on — that your assistant reads before it answers anything about the business. A new conversation starts knowing it instead of being told it again.
- Research. Search X, Bluesky, Hacker News and GitHub. Only X counts against your allowance; the other three are free and unlimited. Asking for posts above an impression floor costs more reads and can honestly come back empty — which is the point, since ranking ten mediocre posts will always name a winner.
- Publish. Post and schedule to X. Publishing is irreversible — the post is public the moment it lands.
- Remember. Up to 50 saved profiles across all four sources, with your own note on why each one matters, plus notes on your voice and audience. Free, and none of it metered. Nothing is ever saved automatically — your assistant saves a profile when you ask it to, and not otherwise.
- Measure. Your own follower and post history, captured over time, because the platforms will not tell you what a number was last month.
Allowances
One plan. It includes 1,500 paid post reads and 100 published posts a month. When the read allowance runs out, live reads from X pause and everything else keeps working — saved profiles, history, scheduling and publishing are all unaffected. Your assistant can check what is left at any time.
Limitations, stated up front
- No replies or quote posts yet. You read here and reply on X.
- Posts containing links are not supported. X charges roughly thirteen times more for them, and there is no way around it — a reply carrying a link costs the same.
- No AI writer of our own. Your assistant does the thinking; this gives it hands, eyes and memory.
Connecting your business accounts
Optional and read-only. Search Console, Vercel and Supabase are a single click through that provider’s own consent screen. Stripe connects either through the Muridian Stripe App, whose install screen lists every permission it asks for, or with a restricted, read-only key you create in your Stripe dashboard and paste. Either way the access is read-only: it cannot charge a card, issue a refund or move a payout.
- Stripe — revenue, subscriptions, trials, churn and failed payments. We never write to your account and never move money.
- Google Search Console — clicks, impressions, CTR and average position for properties you choose, split into branded and non-branded searches. Google anonymises this before we see it, and the branded split is inferred by matching your own name and domain, not something Google labels.
- Vercel — deployment history and Web Analytics aggregates.
- Supabase — database size, table growth and advisor findings, read through a read-only role. We cannot read the contents of your tables, and neither can your assistant: the query set is fixed in code and cannot be extended by anyone.
How current the numbers are
Every figure is dated, everywhere it appears, because “MRR is $4,200” and “MRR was $4,200 when we last looked” are different claims and only one of them is ours to make.
- Stripe, Vercel and Supabase are captured daily and refreshed on demand when your assistant asks and the stored figure is over an hour old. If that refresh returns nothing, you are told the numbers are the last successful capture rather than being shown them as current.
- Search Console lags about two days, by Google’s design, and we do not paper over it. The period shown ends before today and asking again will not make it more recent. A tool that re-fetched on demand would return identical figures and charge you for the privilege.
- X posts and follower counts are collected on a schedule: new posts are looked for at most twice a day automatically and up to four more times a day when you press Check for new posts. Each tracked post is re-read daily for its first week and about twice a week after that, up to 30 days. A post collected late has no readings from before it was seen.
Anything Muridian shows you about how these relate over time is a correlation. It can tell you that you published something and that traffic moved. It cannot tell you one caused the other, and it does not claim to. There is no attribution here, no prediction of what will spread, and nothing that acts on your behalf without being asked.
Help
Email letin1672@gmail.com. See also the support page, the terms and the privacy policy.