flarum-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLARUM_EMAIL | No | Your Flarum email (alternative to username) | |
| FLARUM_BASE_URL | No | Base URL of the Flarum forum | https://reverser.id |
| FLARUM_PASSWORD | No | Your Flarum password | |
| FLARUM_USERNAME | No | Your Flarum username (alternative to email) | |
| FLARUM_API_TOKEN | No | Pre-generated API token (alternative to username/password) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tagsA | List every category/tag on the reverser.id forum with its numeric id, slug, and discussion count. Use the ids here when creating a discussion. |
| search_discussionsB | Full-text search discussions on the forum. Returns matching titles with id, author, and tags. |
| recent_discussionsB | List the most recently active discussions on the forum. |
| discussions_by_tagA | List discussions filed under a given tag (category), by tag slug — e.g. 'malware-analysis'. |
| get_discussionA | Fetch a discussion by id, including its posts rendered as plain text. |
| create_discussionA | Start a new discussion (requires REVERSER_API_TOKEN). Flarum needs at least one primary tag — pass tag ids from list_tags. Content is Markdown. |
| reply_to_discussionA | Post a reply to an existing discussion (requires REVERSER_API_TOKEN). Content is Markdown. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action or query (create, list-by-tag, get, list-tags, recent, reply, search) with no overlap in functionality.
Most tools follow verb_noun pattern with snake_case, but 'discussions_by_tag' and 'recent_discussions' deviate slightly (preposition, adjective-first) from the dominant pattern.
7 tools is a reasonable count for a forum MCP, covering essential operations without being too sparse or bloated.
Covers create, read (by ID, by tag, recent, search), and reply; missing update and delete capabilities, but core read/write workflows are present.