MCP for Flarum
Related Servers
Alternatives to MCP for Flarum
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact directly with NodeBB forums by searching, reading, posting, editing, and moderating content through standard MCP transports with scoped permissions.7 npmBSD 2-Clause "Simplified"
- AlicenseAqualityBmaintenanceMCP server for Flarum forums that enables searching, reading, and posting discussions through Flarum's REST API.715 npmMIT
- FlicenseAqualityCmaintenanceEnables an AI agent to read and act on a single Discourse forum as one user, including posting, private messages, likes, reactions, bookmarks, watch/track/mute, and reading its own notifications via a stdio MCP server.8-
- AlicenseNot gradedqualityCmaintenanceMCP server for NodeBB forums that enables AI assistants to access forum data, search topics, and perform semantic search via the Model Context Protocol.19 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to read public forum threads, start discussions, and post replies via HTTP and JSON, with optional authenticated write access.MIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive Discord MCP server enabling AI assistants to run a Discord community through 111 tools for messaging, moderation, roles, channels, forums, webhooks, and more, plus a raw REST API passthrough for full Discord API access.MIT
TDQS
Scored across 15 tools
Most tools have clear roles, and the generic CRUD verbs (flarum_create/update/delete) are easy to distinguish from the docs and reference tools. However, flarum_list vs flarum_search and flarum_create vs flarum_create_discussion overlap in behavior, even though the descriptions point to the specialized helper being more convenient.
All tools share the flarum_ prefix and use readable verbs, but the conventions are mixed: core API verbs are single-word (flarum_get, flarum_update), docs tools reverse the order (flarum_docs_get, flarum_docs_search), and flarum_create_discussion follows verb_noun. flarum_whoami, flarum_dev, and flarum_troubleshoot are standalone names that don't fit a verb_noun pattern.
Fifteen tools is within the ideal range and matches a broad purpose: Flarum API CRUD, discussion helpers, documentation lookup, and admin/dev guidance. The generic resource tools plus convenience wrappers and an escape hatch give the set a clear rationale without feeling bloated.
The generic flarum_list/get/create/update/delete tools provide near-complete lifecycle coverage for any Flarum resource, and flarum_request covers any remaining API endpoint. Discussion creation/reply, docs search/get, and whoami cover the main forum-administration and learning workflows, leaving no obvious dead ends.