Focalboard MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FOCALBOARD_HOST | Yes | The URL of your Focalboard instance (e.g., https://focalboard.example.com) | |
| FOCALBOARD_PASSWORD | Yes | Your Focalboard password | |
| FOCALBOARD_USERNAME | Yes | Your Focalboard username or email |
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 |
|---|---|
| list_boardsB | List all boards for a team. Returns an array of boards with their IDs, titles, and properties. |
| get_boardC | Get detailed information about a specific board, including all its columns and property definitions. |
| search_boardsC | Search for boards by name or keyword within a team. |
| create_cardC | Create a new card (task) in a board. You can set the title, properties, description, and column placement. |
| get_cardsA | List all cards (tasks) in a board with pagination support. |
| get_cardC | Get detailed information about a specific card by its ID. |
| update_cardC | Update a card's properties, including moving it to different columns. Accepts human-readable property and column names. |
| delete_cardB | Delete a card (task) from a board permanently. |
| add_card_descriptionB | Add or set description/content to a card. Creates a new text block with markdown content. |
| get_card_contentC | Get all content blocks (descriptions) for a card. |
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 10 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, 'get_card' retrieves card metadata, while 'get_card_content' fetches its content blocks, and 'add_card_description' specifically modifies descriptions. The tools cover different resources (boards vs. cards) and actions (create, get, update, delete, list, search) without overlap.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'create_card', 'get_board', and 'update_card'. This predictability makes it easy for agents to understand and select the right tool based on the intended action and resource.
With 10 tools, this server is well-scoped for managing boards and cards in a project management context. Each tool earns its place by covering essential operations like CRUD for cards, board listing and searching, and content management, without being overly sparse or bloated.
The tool surface provides complete CRUD and lifecycle coverage for the domain of board and card management. It includes creation, retrieval, updating, and deletion of cards, along with board listing, searching, and detailed access. No obvious gaps exist, ensuring agents can handle full workflows without dead ends.