飞书MCP机器人

Created By
Chenzhi-Anaa year ago
飞书MCP服务器,用于通过MCP协议向飞书发送消息
Overview

what is 飞书MCP机器人?

飞书MCP机器人 is a server that acts as a proxy to send messages to Feishu using the MCP protocol, allowing users of Claude or Cursor to execute business logic with the Feishu bot combined with LLM models.

how to use 飞书MCP机器人?

To use the 飞书MCP机器人, configure the server by replacing the directory path and webhook address in the command: uv --directory YOUR_PATH run bot.py --webhook YOUR_WEB_HOOK. You can also install it automatically via Smithery using the command: npx -y @smithery/cli install @Chenzhi-Ana/feishu_mcp_server --client claude.

key features of 飞书MCP机器人?

  • Acts as a bridge between Claude/Cursor and Feishu bot.
  • Facilitates interaction with Feishu API through MCP protocol.
  • Supports business logic execution using LLM models.

use cases of 飞书MCP机器人?

  1. Automating business processes through Feishu bot.
  2. Integrating AI models with messaging services.
  3. Enhancing communication workflows in organizations.

FAQ from 飞书MCP机器人?

  • What is the purpose of 飞书MCP机器人?

It allows users to leverage AI models to interact with Feishu for executing business logic.

  • How do I install 飞书MCP机器人?

You can install it via Smithery or manually by configuring the server with your specific paths and webhook.

  • Can I use 飞书MCP机器人 with other AI models?

Yes, it is designed to work with Claude and Cursor, but can be adapted for other models.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Chenzhi-Ana
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago