mastodon-mcp
Related Servers
Alternatives to mastodon-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI models to interact with a Mastodon account, including viewing the home timeline, posting statuses, and checking notifications.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to write, schedule, publish, and measure social media posts across LinkedIn, Bluesky, Mastodon, and YouTube, plus manage media and queue slots, through one OAuth URL with no install or API key. It also covers retrying, cancelling, restoring posts and reading analytics, with reversibility safeguards around irreversible publishing.MIT
- FlicenseBqualityDmaintenanceEnables AI agents to control Instagram accounts programmatically, supporting profile management, media interaction, direct messaging, and follower management.132-
- AlicenseAqualityBmaintenanceEnables AI agents to post, reply, run threads, read timelines, search, manage follows, and analyze engagement on Bluesky, with setup requiring only a handle and app password.41MIT
- AlicenseAqualityAmaintenanceEnables AI agents to manage a Threads profile through Meta's API, including posting, threads, replies, reply moderation, and insights.3035 npm1MIT
- AlicenseCqualityAmaintenanceComprehensive MCP server for Mastodon integration, enabling AI assistants to read timelines, post statuses, manage accounts, search, and more on any Mastodon instance.543MIT
TDQS
Scored across 76 tools
Most tools target a distinct resource and action, and the descriptions carefully disambiguate the five timeline getters and reverse pairs like get_favourites vs get_favourited_by. A few names require close reading, but after reading the descriptions there is no real role overlap.
The dominant pattern is verb_noun snake_case with clear get/action prefixes, and paired actions like follow_account/unfollow_account are predictable. Minor exceptions such as whoami, report, and get_favourited_by/get_boosted_by keep it from being perfectly uniform.
76 tools is far beyond the 3-15 range that makes a tool set scannable, and even though each tool maps to a real Mastodon endpoint, the surface is heavy for an agent to navigate. It is too many rather than a coherent minimal set.
Statuses, timelines, interactions, lists, notifications, moderation, and the account graph are all covered with read and write operations, so core workflows have no dead ends. Missing write actions for profile avatar/header and endorsements are the main minor gaps.