Favro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAVRO_EMAIL | Yes | Your Favro account email address used for API authentication. | |
| FAVRO_API_TOKEN | Yes | Your Favro API token created in My Profile -> API Tokens. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_boardsA | List boards in the organization. By default, lists boards at the TOP LEVEL only (not inside collections/folders). To find boards inside a collection:
|
| get_boardB | Get details of a specific board including its columns. |
| get_current_boardA | Get details of the currently selected board. Returns: The board details or a message if none is selected. |
| set_boardA | Select a board as the active board. This sets the default board for card operations. The board can be specified by ID or name. |
| list_cardsC | List cards on a specific board with pagination. |
| list_custom_fieldsB | List custom fields in the organization. |
| get_card_detailsC | Get detailed information about a specific card. |
| add_commentC | Add a comment to a card. |
| create_cardC | Create a new card. |
| update_cardC | Update a card's properties. |
| move_cardA | Move a card to a different column and/or lane, optionally on another board. Specify a column, a lane, a place in the column, or a combination. Lanes only apply to boards with lanes enabled; use list_lanes to see available lanes. To place the card in the column's order, give at most one of position, before, or after. Without column and lane, the card is reordered within its current column. The order is shared by the whole column, across lanes. A card can be committed to several boards at once. Favro's API treats a board change as "commit" (add to the target board, keep the original) by default, which looks like a copy; this tool uses "move" so a cross-board move actually relocates the card. |
| assign_cardC | Assign or unassign a user from a card. |
| tag_cardC | Add or remove a tag from a card. |
| delete_cardC | Delete a card. |
| upload_attachmentB | Upload a file attachment to a card. |
| list_collectionsA | List all collections (folders) in the organization. Collections are folders that contain boards. If you're looking for a board but can't find it with list_boards, it may be inside a collection. Use the collection name with list_boards(collection="name") to see boards inside that collection. Returns: A list of collections with their IDs and names. |
| list_columnsB | List all columns on a specific board. |
| create_columnC | Create a new column on a board. |
| rename_columnC | Rename a column. |
| move_columnC | Move a column to a new position. |
| delete_columnA | Delete a column from a board. Warning: This will also delete all cards in the column! |
| list_lanesA | List the lanes (swimlanes) on a board. Lanes are read-only in the Favro API and cannot be created, renamed, or
deleted. Use a returned lane_id as the |
| list_organizationsA | List all organizations accessible to the authenticated user. Returns: A list of organizations with their IDs, names, and member counts. Use set_organization tool to select one as the active organization. |
| get_current_organizationA | Get details of the currently selected organization. Returns: The organization details or a message if none is selected. |
| set_organizationB | Select an organization as the active organization. The organization can be specified by ID or name. |
| list_tagsC | List tags in the organization. |
| list_usersC | List users in the current organization. |
| get_userA | Look up a user by ID, name, or email address. Useful for resolving user IDs returned in card details (e.g. assignments, comments) to human-readable user information. |
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 28 tools
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.
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.
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.
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.