Lark MCP Server

Created By
junyuan-qia year ago
Overview

What is Lark MCP Server?

Lark MCP Server is a Model Context Protocol (MCP) server implementation designed for Lark/Feishu, enabling MCP-compatible applications to interact with Lark's collaboration capabilities.

How to use Lark MCP Server?

To use Lark MCP Server, clone the repository, install dependencies, and build the project. Connect it with an MCP client like Claude Desktop by configuring the necessary settings in the claude_desktop_config.json file.

Key features of Lark MCP Server?

  • Message Sending: Allows AI models to send direct messages to Lark users.
  • Calendar Management:
    • List events within a specific time range.
    • Create new calendar events with customizable details.
    • Add various types of attendees to events (users, groups, meeting rooms, external emails).

Use cases of Lark MCP Server?

  1. Integrating AI assistants with Lark for enhanced communication.
  2. Automating calendar event management through AI models.
  3. Facilitating real-time messaging between AI applications and Lark users.

FAQ from Lark MCP Server?

  • What are the prerequisites for using Lark MCP Server?

You need Node.js v18 or higher, a registered Lark/Feishu application, and a user access token for calendar operations.

  • How do I troubleshoot issues with the server?

Check the server logs for detailed error information, and ensure all environment variables and access tokens are correctly set.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
junyuan-qi
Star
1
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

16 hours ago
Voyei

6 hours ago