home / mcp / feishu project mcp server
一个可以读取飞书项目需求、评论需求、流转需求等的MCP。
Configuration
View docs{
"mcpServers": {
"im47cn-feishu-project-mcp": {
"command": "node",
"args": [
"/path/to/feishu-project-mcp/dist/index.js"
],
"env": {
"HOST": "localhost",
"PORT": "3000",
"LOG_DIR": "./logs",
"LOG_LEVEL": "info",
"STORAGE_DIR": "./storage",
"FEISHU_APP_ID": "your_app_id",
"CHECK_INTERVAL": "5000",
"FEISHU_API_URL": "https://project.feishu.cn/open_api",
"FEISHU_APP_SECRET": "your_app_secret",
"MAX_CONCURRENT_TASKS": "5"
}
}
}
}You deploy and run the Feishu Project MCP Server to manage end-to-end requirements, development workflows, and automated code submissions from Feishu projects. It integrates Feishu data, analyzes needs, generates technical plans, guides implementation, and keeps your project synchronized with version control and project status Updates.
You interact with the Feishu Project MCP Server through an MCP client. The server exposes a standard interface for health checks and a set of MCP tools that cover project and requirement management, analysis, and implementation workflows. You can run the server locally and connect to it from your MCP client or configure an integration in your workflow automation tool to invoke the available MCP endpoints and tools.
Prerequisites: Node.js 18 or later. A Feishu project system account and API credentials.
Install steps you can follow to get started on a typical development machine:
# Clone the repository
git clone https://github.com/yourusername/feishu-project-mcp.git
cd feishu-project-mcp
# Install dependencies
npm installCreate a .env file to configure the Feishu API connection and service parameters. The following environment variables are used directly by the MCP server:
# Feishu API Configuration
FEISHU_APP_ID=your_app_id
FEISHU_APP_SECRET=your_app_secret
FEISHU_API_URL=https://project.feishu.cn/open_api
# Service Configuration
CHECK_INTERVAL=5000
STORAGE_DIR=./storage
LOG_DIR=./logs
LOG_LEVEL=info
MAX_CONCURRENT_TASKS=5
# Server Configuration
PORT=3000
HOST=localhostYou can run the server in development mode or build it for production, then start the service.
Development mode command:
npm run devProduction mode sequence (build and start):
npm run build
npm startConfigure MCP services in your Cline environment by adding a new MCP server entry. The following examples show two valid approaches you may configure in your MCP settings.
"feishu_mcp": {
"command": "node",
"args": [
"/path/to/feishu-project-mcp/dist/index.js"
],
"env": {
"FEISHU_APP_ID": "your_app_id",
"FEISHU_APP_SECRET": "your_app_secret",
"FEISHU_API_URL": "https://project.feishu.cn/open_api"
},
"disabled": false,
"alwaysAllow": [
"health",
"health.components",
"health.integrations",
"health.tasks",
"health.memory",
"feishu.projects",
"feishu.requirements",
"feishu.bugs",
"task.create",
"task.get",
"mode.analyze",
"mode.implement"
]
}Another common approach uses npx to run the MCP server from the package name, useful after publishing the package to a registry. The following shows the intended configuration for local testing or publishing use.
"feishu-mcp_npx": {
"command": "npx",
"args": [
"feishu-project-mcp"
],
"env": {
"FEISHU_APP_ID": "your_app_id",
"FEISHU_APP_SECRET": "your_app_secret",
"FEISHU_API_URL": "https://project.feishu.cn/open_api"
},
"disabled": false,
"alwaysAllow": [
"health",
"health.components",
"health.integrations",
"health.tasks",
"health.memory",
"feishu.projects",
"feishu.requirements",
"feishu.bugs",
"task.create",
"task.get",
"mode.analyze",
"mode.implement"
]
}Keep your Feishu API credentials secure. Do not hard-code sensitive values in source code. Use environment variables and a secret management mechanism in production. Regularly rotate FEISHU_APP_SECRET and monitor access to the MCP server.
If the server fails to start, verify that Node.js 18+ is installed, required environment variables are set, and the port is not in use by another process. Check the logs directory for error messages and confirm that the Feishu API URL is reachable.
Retrieve the complete health status of the MCP server including component, integration, task, and memory information.
Check health status of individual components in the MCP system.
Get health status of external integrations connected to the MCP server.
Inspect health and progress of internal tasks.
Report current memory usage and performance metrics.
Fetch the list of Feishu projects accessible to the MCP server.
Fetch the list of requirements for a given Feishu project.
Fetch the list of bugs or defects for a Feishu project.
Create a new internal MCP task.
Retrieve details for a specific MCP task.
Analyze a requirement or defect to derive insights and questions.
Implement the analyzed requirement or fix in code according to the plan.