Skip to main content
Glama
enesjakozh
NINGyv179

MCP-FEISHU

by NINGyv179
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

MCP飞书

MCP-FEISHU 是一款专为 Windsurf IDE 集成设计的微服务控制平面 (MCP) 服务器。它从飞书 OpenAPI 获取 API 信息，并将其提供给 IDE 的 MCP 客户端，从而实现开发环境中 API 的无缝集成和管理。

特征

  • 连接飞书OpenAPI获取API规范

  • 将 API 信息公开为 MCP 资源

  • 提供 API 发现和探索工具

  • 支持 Windsurf IDE 中的 API 测试和集成

  • 实现模型上下文协议 (MCP) 以实现标准化通信

Related MCP server: Lark MCP Server

安装

# 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

用法

启动服务器

pnpm start

调试

npx @modelcontextprotocol/inspector node dist/index.js

从 Windsurf IDE 连接

pnpm build

在您的 Windsurf IDE 设置中，添加一个具有以下配置的新 MCP 服务器：

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

API 资源

MCP-FEISHU 服务器开放以下资源：

  • api://projects - 列出所有 API 项目

  • api://projects/{projectId} - 获取特定项目的详细信息

  • api://projects/{projectId}/apis - 列出项目中的所有 API

  • api://projects/{projectId}/apis/{apiId} - 获取特定 API 的详细信息

工具

该服务器提供以下工具：

  • get_defect_link - 获取特定缺陷的链接

  • get_recently_updated_defect_list - 获取最近更新的缺陷列表

发展

# Run in development mode with hot reloading
npm run dev

执照

麻省理工学院

Available Tools

2 tools
get_recently_updated_defect_listD
ParametersJSON Schema
NameRequiredDescriptionDefault
statusYes
startDateYes
endDateYes

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.

  1. 2 tool updates
    • First observedget_defect_link
    • First observedget_recently_updated_defect_list
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

D1.7/5.0

Scored across 2 tools

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

Related MCP Connectors

Related MCP Servers

  • MCP-APIKit

    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.
    6
    -

  • Lark MCP Server

    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.
    22 npm
    3
    -

  • reasonix-feishu-mcp

    Monc618
    A
    license
    Not graded
    quality
    C
    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.
    MIT

Appeared in Searches