fedi-mcpWhat is this?
fedi-mcp is a self-hosted gateway that puts your Mastodon, GotoSocial, and Bluesky accounts in front of your AI tools. It speaks the Model Context Protocol (MCP), so MCP-aware clients like Claude can read timelines, post, search, follow, and more — across every account you link, each kept private to your own login.
What it does
- • Gives every account its own isolated set of linked social accounts — your credentials are never reachable by anyone else.
- • One consistent tool set across networks (post_status, get_home_timeline, reblog, favourite, …), with a few provider-specific extras.
- • Stores each account's token / app password encrypted at rest and decrypts it only to make a call on your behalf.
- • Keeps an audit log of the calls made through your account.
Getting started
- 1. Create an account. Registration is open — sign up with a passkey (Touch ID, Windows Hello, a security key, or your phone).
- 2. Link a social account. Under Accounts, link Mastodon/GotoSocial (instance URL + access token, or OAuth) or Bluesky (handle + app password, or OAuth).
- 3. Connect your MCP client. Either authorize via OAuth (clients like Claude point at the endpoint and you approve with your passkey), or create an API token under Tokens and send it as Authorization: Bearer <token>.
- 4. Discover tools. There's one shared tool set; each tool takes an account argument (your account's slug). Call list_connections to see your accounts and the tools each one supports.
About your credentials
Tokens and app passwords are encrypted at rest and scoped to your account alone. Still, this is a personal, best-effort project — so use a narrowly-scoped token or a dedicated app password, and revoke it on the instance the moment you stop using it. Full details are in the privacy & disclaimer.
Don't want to trust someone else's server with your credentials? Fair — fedi-mcp is open source and self-hostable, so you can run your own instance and be the only one you have to trust.