How do I use MCP-FEISHU?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP-FEISHU list all APIs in the authentication project" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

MCP-FEISHU

by NINGyv179

Overview Schema Related Servers Score Discussions

TypeScript

Remote

MCP-FEISHU

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.

Features

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

Related MCP server: Lark MCP Server

Installation

# Clone the repository
# git clone https://github.com/yourusername/mcp-feishu.git
# cd mcp-feishu

# Install dependencies
pnpm install

# Build the project
pnpm run build

Usage

Starting the Server

pnpm start

Debug

npx @modelcontextprotocol/inspector node dist/index.js

Connecting from Windsurf IDE

pnpm build

In your Windsurf IDE settings, add a new MCP server with the following configuration:

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

API Resources

The MCP-FEISHU server exposes the following resources:

api://projects - List all API projects
api://projects/{projectId} - Get details for a specific project
api://projects/{projectId}/apis - List all APIs in a project
api://projects/{projectId}/apis/{apiId} - Get details for a specific API

Tools

The server provides the following tools:

get_defect_link - Get the link to a specific defect
get_recently_updated_defect_list - Get a list of recently updated defects

Development

# Run in development mode with hot reloading
npm run dev

License

MIT

Available Tools

2 tools

get_defect_linkD

ParametersJSON Schema

Name	Required	Description	Default
`ID`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_recently_updated_defect_listD

ParametersJSON Schema

Name	Required	Description	Default
`status`	Yes
`startDate`	Yes
`endDate`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesAug 15, 2025
- First observedget_defect_link
- First observedget_recently_updated_defect_list

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

D1.7/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves a specific defect link, while the other fetches a list of recently updated defects. There is no overlap or ambiguity between them.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming. The naming is predictable and uniform across the set.

Tool Count2/5

With only 2 tools, the server feels thin for a domain like defect management in Feishu. This minimal set lacks essential operations like creating, updating, or deleting defects, making it under-scoped.

Completeness1/5

The tool surface is severely incomplete for defect management. It only provides read-only access to defects (link and list), missing critical CRUD operations such as create, update, delete, or search, which will cause agent failures in handling defect workflows.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

microservices.sh
sh.microservices
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud Platforms Agent Orchestration Developer Tools
21
InsForgeOAuth
io.github.InsForge
MCP server for InsForge BaaS — database, storage, edge functions, and deployments
Cloud Platforms Databases Cloud Storage
235
jumpcloud-genaiOAuth
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2
SupabaseOAuth
com.supabase
MCP server for interacting with the Supabase platform
Cloud Platforms Databases Developer Tools
32,890

Related MCP Servers

MCP-APIKit
Developer Tools API Testing Code Execution
scarqin
F
license
C
quality
D
maintenance
A microservice control plane server that integrates with Windsurf IDE by fetching API information from Eolink OpenAPI and exposing it as MCP resources, enabling seamless API integration and management in the development environment.
Updated a year ago (2025-03-18 15:29 UTC)
6
-
Lark MCP Server
Communication Developer Tools
lorrylockie
F
license
Not graded
quality
D
maintenance
A server that enables LLMs to interact with Lark/Feishu services, currently supporting employee information queries via Lark's Contact API.
Updated 2 years ago (2025-03-04 02:11 UTC)
32
3
-
reasonix-feishu-mcp
Communication Workplace & Productivity
Monc618
A
license
Not graded
quality
B
maintenance
MCP server for Feishu/Lark API integration, enabling AI agents to send messages, manage groups, create and edit documents and spreadsheets, and search knowledge bases.
Updated 3 months ago (2026-06-19 14:47 UTC)
MIT
feishu-wiki-mcp
Workplace & Productivity Communication Knowledge & Memory
akakenle
A
license
B
quality
D
maintenance
An MCP server that exposes Feishu (Lark) APIs as standardized tools, enabling knowledge base, document, spreadsheet, and IM operations through any MCP client.
Updated 7 months ago (2026-02-20 10:18 UTC)
36
21
MIT

Appeared in Searches

Information about Feishu (Lark) collaboration platform

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/NINGyv179/mcp-feishu'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

MCP-FEISHU

Features

Installation

Usage

Starting the Server

Debug

Connecting from Windsurf IDE

API Resources

Tools

Development

License

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

MCP-APIKit

Lark MCP Server

reasonix-feishu-mcp

feishu-wiki-mcp

Appeared in Searches

Latest Blog Posts

MCP directory API