repo-template

Created By
loonghaoa year ago
A Python server implementation for Feishu (Lark) bot that follows the Model Context Protocol (MCP). This server provides a standardized interface for handling automated messaging and context-aware interactions within enterprise Feishu environments.
Overview

what is Feishu Bot MCP Server?

Feishu Bot MCP Server is a Python server implementation designed for the Feishu (Lark) bot, adhering to the Model Context Protocol (MCP). It provides a standardized interface for automated messaging and context-aware interactions in enterprise Feishu environments.

how to use Feishu Bot MCP Server?

To use the Feishu Bot MCP Server, clone the repository from GitHub, set up your Python environment, and configure the server with your Feishu bot credentials. You can then deploy the server to handle messaging and interactions.

key features of Feishu Bot MCP Server?

  • Standardized interface for bot interactions
  • Support for automated messaging
  • Context-aware interaction handling

use cases of Feishu Bot MCP Server?

  1. Automating responses in enterprise communication.
  2. Enhancing user interactions with context-aware messaging.
  3. Integrating with other enterprise tools for seamless communication.

FAQ from Feishu Bot MCP Server?

  • What programming language is used?

The server is implemented in Python.

  • Is this server suitable for production use?

Yes, it is designed for enterprise environments and can be deployed in production.

  • Where can I find the documentation?

Documentation can be found in the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
loonghao
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago