Skip to main content
Glama
enesjakozh
NINGyv179

MCP-FEISHU

by NINGyv179
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

MCP-フェイシュ

MCP-FEISHUは、Windsurf IDEとの統合に特化して設計されたマイクロサービスコントロールプレーン（MCP）サーバーです。Feishu OpenAPIからAPI情報を取得し、IDEのMCPクライアントに提供することで、開発環境内でシームレスなAPI統合と管理を実現します。

特徴

  • Feishu 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