MCP Feishu MCP Server

MCP server for Windsurf that integrates with Feishu OpenAPI

Local serverstdio

What is the MCP Feishu MCP server?

Mcp feishu mcp server connects MCP Feishu to AI assistants that speak the Model Context Protocol. MCP server for Windsurf that integrates with Feishu OpenAPI.

What MCP Feishu does

MCP-FEISHU is a microservice control plane (MCP) server designed specifically for Windsurf IDE integration. It fetches API information from Feishu OpenAPI and provides it to the IDE's MCP client, enabling seamless API integration and management within your development environment.

Key capabilities

  • Connects to Feishu OpenAPI to retrieve API specifications
  • Exposes API information as MCP resources
  • Provides tools for API discovery and exploration
  • Supports API testing and integration within Windsurf IDE
  • Implements the Model Context Protocol (MCP) for standardized communication

Tools it exposes

Once connected, the assistant can call these 4 tools directly:

  • api — //projects - List all API projects
  • get_defect_link — Get the link to a specific defect
  • get_recently_updated_defect_list — Get a list of recently updated defects
  • Debug — The Debug tool exposed by this server

Installing the mcp feishu mcp server

The server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 4 environment variables: APP_ID, APP_SECRET, TABLE_ID, APP_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP Feishu sits in that group, and the shape of its toolset — api, get_defect_link, get_recently_updated_defect_list among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by NINGyv179.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp feishu mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
api//projects - List all API projects
get_defect_linkGet the link to a specific defect
get_recently_updated_defect_listGet a list of recently updated defects
DebugThe Debug tool exposed by this server.

How to install the MCP Feishu MCP server

"mcpServers": {
      "feiShuServer": {
        "command": "node",
        "args": ["/Program Files/project/mcp-feishu/dist/index.js"],
        "env": {
          "APP_ID": "",
          "APP_SECRET": "",
          "TABLE_ID": "",
          "APP_TOKEN": ""
        }
      }
    }

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
APP_IDConfiguration value read at startup.Optional
APP_SECRETCredential the server authenticates with.Yes
TABLE_IDConfiguration value read at startup.Optional
APP_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP Feishu to api.
  • Use MCP Feishu to get defect link.
  • Use MCP Feishu to get recently updated defect list.

Frequently asked questions

It connects MCP Feishu to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (api, get_defect_link, get_recently_updated_defect_list, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Feishu directly.