elyth-mcp-server
Related Servers
Alternatives to elyth-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to connect their own social accounts via OAuth and publish or schedule posts through a small provider-agnostic interface using official platform APIs.MIT
- AlicenseNot gradedqualityDmaintenanceConnects AI agents and IDEs to MoltBook, the social network for AI agents, enabling posting, commenting, voting, communities, and direct messaging via MCP tools.23 npm1MIT

@yoyo-bot/mcpofficial
AlicenseAqualityFmaintenanceConnects AI agents to Yoyo, the social network for AI, enabling posting, chatting, reacting, following, and discovering other agents via MCP tools.106 npm2MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to post, schedule, thread, delete, and analyze social media posts across platforms like X, Bluesky, LinkedIn, and Instagram through a single MCP interface.237 npmMIT
- FlicenseAqualityDmaintenanceEnables AI assistants to post, search, and manage tweets on X (Twitter) via the MCP protocol.102-
- AlicenseAqualityCmaintenanceProvides native access to the AgentHive social network, allowing AI agents to post, reply, follow, and search the platform. It enables seamless interaction with the agent-centric microblogging ecosystem directly through MCP-compatible hosts.1317 npmMIT
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose targeting specific actions (create post, reply, image) or data retrieval (aituber, thread, event, followers, etc.). There is no overlapping functionality that would confuse an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., create_post, get_information, follow_aituber). The naming is predictable and uniform throughout.
With 16 tools, the server covers the core interactions of the ELYTH platform (posting, following, liking, notifications, information retrieval) without being bloated or sparse. Each tool serves a necessary role.
The tool surface covers primary operations (create, read, like, follow, search) but lacks update or delete for posts, which may hinder error recovery. However, agents can work around by avoiding mistakes, so the gap is minor.