A
licenseA
qualityC
maintenanceRead-only MCP server for Favro, providing tools to list organizations, collections, boards, cards, comments, checklists, and search cards via the Favro API.
14
8 npm
1
MIT
Favro MCP
by truls27a
Related Servers
Alternatives to Favro MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to manage tasks, boards, lists, and comments on a Kanban-style project management system through JSON-RPC methods.1 npm2AGPL 3.0
- FlicenseNot gradedqualityDmaintenanceThis is an MCP Server for Trello that enables interaction with Trello's API through natural language, allowing management of boards, cards, lists, and other Trello resources.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Kaiten project management through its REST API. Enables managing spaces, boards, cards, comments, checklists, tags, and time logs.1MIT
- AlicenseAqualityCmaintenanceMCP server for Fizzy kanban task management with tools for boards, cards, comments, and checklists.756 npm3AGPL 3.0
- AlicenseAqualityFmaintenanceMCP server enabling AI agents to manage PLANKA kanban boards with full CRUD support for cards, tasks, labels, comments, and lists.15129 npm11MIT
TDQS
B3.2/5.0
Scored across 28 tools
Disambiguation4/5
Most tools target a distinct resource+action (card CRUD, column CRUD, board lookup, org selection), and paired tools like set_board/get_current_board are clearly differentiated. Minor overlap exists where update_card's broad 'update a card's properties' could blur with the more specific move_card/assign_card/tag_card, but the descriptions disambiguate well.
Naming Consistency5/5
Every tool follows a clean snake_case verb_noun pattern (list_boards, create_card, move_column, delete_card, set_organization). The naming is highly predictable with only trivial variations like get_card_details vs. get_board.
Tool Count3/5
At 28 tools this is on the heavy side, though the breadth of the Favro domain (orgs, collections, boards, columns, lanes, cards, users, tags) justifies many of them. It sits at the borderline where the surface feels large and could likely be consolidated.
Completeness4/5
Card operations (create/get/update/move/assign/tag/delete/comment/attachment) and column operations (full CRUD) are comprehensive, covering the primary workflows. However board creation/update/deletion and tag/collection management are absent, leaving some lifecycle gaps the agent must work around.
Maintenance
ActivityMaintained
ResponsivenessWithin a week