get_defect_linkLABSCO SUMMARY
The defect list comes to the editor instead of the other way round.
Two tools, both aimed at the same moment: you are in the IDE, something is broken, and the ticket lives in Feishu. The API resources sit behind them for when you need the specification rather than the defect.
What it is
A Feishu server built for Windsurf. It reads API information from Feishu OpenAPI, exposes API projects and their endpoints as resources, and provides two defect tools.
What you get
- A list of recently updated defects
- The link to a specific defect
- API projects and the APIs inside them, addressable as resources
Requirements
A Feishu app - its ID and secret, plus the table and app token identifying the base it reads - all four set in the MCP client config. Node, with the project built before first run.
Setup effort
Build from source — git clone https://github.com/NINGyv179/mcp-feishu.git
USE CASES
01
Picking up what changed on the defect board
Read the recently updated defects without leaving the editor, so the list is current when you choose what to work on.
02
Getting to the ticket you are about to fix
Find the defect in the recent list and take its link, rather than searching Feishu for it by hand.
03
Sharing a defect with someone in the thread
Fetch the direct link and paste it where the conversation is happening.
2 tools
Listed in project docs. Your client may show a different list.
get_recently_updated_defect_listBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation. The shipped tools are defect-board tools, get_defect_link and get_recently_updated_defect_list; the Feishu OpenAPI spec features are resources, not tools.
Requires
- APP_ID in your environment
- APP_SECRET in your environment
- APP_TOKEN in your environment
- TABLE_ID in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
# Clone the repository
git clone https://github.com/NINGyv179/mcp-feishu.git
cd mcp-feishu
# Install dependencies
pnpm install
# Build the project
pnpm run buildMCP Clients
Windsurf
WINDSURF · JSON
{
"mcpServers": {
"feiShuServer": {
"command": "node",
"args": [
"/Program Files/project/mcp-feishu/dist/index.js"
],
"env": {
"APP_ID": "",
"APP_SECRET": "",
"TABLE_ID": "",
"APP_TOKEN": ""
}
}
}
}/Program Files/project/mcp-feishu/dist/index.js is the author's own path; yours is the full path to dist/index.js in your clone. APP_ID and APP_SECRET come from your Feishu app, and TABLE_ID and APP_TOKEN from the Bitable base it reads.
