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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
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_boardA | 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_cardsB | List cards on a specific board with pagination. |
| list_custom_fieldsB | List custom fields in the organization. |
| get_card_detailsA | Get detailed information about a specific card. |
| add_commentB | 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, or both. Lanes only apply to boards with lanes enabled; use list_lanes to see available 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_cardA | 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_columnB | Create a new column on a board. |
| rename_columnC | Rename a column. |
| move_columnB | 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_tagsA | List all tags in the organization. Returns: A list of tags with their IDs, names, and colors. Use the tag name or ID with tag_card() to add/remove tags from cards. |
| list_usersA | List all users in the current organization. Returns: A list of users with their IDs, names, emails, and roles. |
| 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 distinct resources and actions, with clear list/get/create/update/delete patterns. The only mild ambiguity is between get_board and get_current_board, and set_board could initially be mistaken for updating a board rather than selecting the active board, though the descriptions resolve this.
All tool names follow a consistent snake_case verb_noun pattern, using list_ for plural collection retrieval and verbs like create_, update_, move_, delete_ for mutations. Minor variations like add_comment and upload_attachment are still conventional and predictable.
At 28 tools, the surface exceeds the 25+ threshold and will be heavy for an agent to navigate reliably. While each tool is distinct, several read-only get/list utilities and context-selection tools like set_board and set_organization add bulk that could be consolidated.
Card and column workflows are well covered with create/update/move/delete operations, but board lifecycle operations such as create/update/delete board are missing. Comments and attachments also only support one-way actions (add/upload), leaving notable gaps for a project-management integration.