FluentBoards MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOARD_ID | No | Optional: Board ID to enable Board Focus Mode (e.g., 14). When set, operations are scoped to this board only and board manipulation tools are disabled. | |
| WORDPRESS_URL | Yes | The URL of your WordPress site (e.g., https://your-site.local) | |
| ENABLE_DELETES | No | Master switch to enable delete operations (default: false) | false |
| WORDPRESS_USERNAME | Yes | Your WordPress username for authentication | |
| ALLOWED_DELETE_TYPES | No | Comma-separated list of allowed delete types: board,task,label (default: none) | |
| WORDPRESS_APP_PASSWORD | Yes | Your WordPress Application Password for secure authentication | |
| REQUIRE_DELETE_CONFIRMATION | No | Require confirmation parameter for delete operations (default: true) | true |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debug_testB | Test if MCP server is working |
| get_boardB | Get details of a specific board |
| create_stageC | Create a new stage in a board |
| list_tasksC | List tasks in a board |
| get_taskB | Get details of a specific task including comments and attachments |
| create_taskC | Create a new task |
| update_taskC | Update an existing task |
| change_task_statusC | Change the status/stage of a task |
| delete_taskC | Delete a task permanently |
| add_commentC | Add a comment to a task |
| add_labelC | Add a label to a task |
| remove_labelC | Remove a label from a task |
| edit_labelC | Edit a label's title and colors |
| create_labelC | Create a new label on a board |
| delete_labelC | Delete a label from a board permanently |
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 15 tools
Every tool has a clearly distinct purpose with no ambiguity. Tools target specific resources (tasks, labels, stages, boards) and actions (create, get, update, delete, add, remove, change), making it easy for an agent to select the correct tool. For example, 'add_label' vs 'create_label' vs 'remove_label' are clearly differentiated by whether they operate on tasks or boards.
The naming follows a consistent verb_noun pattern throughout with one minor deviation. Most tools use clear action words followed by the resource (e.g., create_task, get_board, update_task). The only inconsistency is 'debug_test', which doesn't follow the domain-specific pattern but is clearly a utility tool.
With 15 tools, this is well-scoped for a project management/board system. Each tool earns its place by covering essential operations for tasks, labels, stages, and boards. The count supports comprehensive workflows without being overwhelming for the domain.
The tool set provides complete CRUD/lifecycle coverage for the domain. It includes creation (create_task, create_label, create_stage), retrieval (get_board, get_task, list_tasks), updates (update_task, change_task_status, edit_label, add_comment, add_label), and deletion (delete_task, delete_label, remove_label). No obvious gaps exist for core board management operations.