Feishu Project

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.

How to use

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.

How to install

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 install

Additional configuration and usage notes

Create 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=localhost

Starting the server

You can run the server in development mode or build it for production, then start the service.

Development mode command:

npm run dev

Production mode sequence (build and start):

npm run build
npm start

Using MCP from Cline (configuration snippets)

Configure 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"
  ]
}

Security and maintenance notes

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.

Troubleshooting

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.

Available tools

health

Retrieve the complete health status of the MCP server including component, integration, task, and memory information.

health.components

Check health status of individual components in the MCP system.

health.integrations

Get health status of external integrations connected to the MCP server.

health.tasks

Inspect health and progress of internal tasks.

health.memory

Report current memory usage and performance metrics.

feishu.projects

Fetch the list of Feishu projects accessible to the MCP server.

feishu.requirements

Fetch the list of requirements for a given Feishu project.

feishu.bugs

Fetch the list of bugs or defects for a Feishu project.

task.create

Create a new internal MCP task.

task.get

Retrieve details for a specific MCP task.

mode.analyze

Analyze a requirement or defect to derive insights and questions.

mode.implement

Implement the analyzed requirement or fix in code according to the plan.