Skip to main content
Glama
Beltran12138

wecom-docs-mcp-server

by Beltran12138
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to wecom-docs-mcp-server

No user-submitted related servers found.

    Related Servers

    • feishu-automation

      ZLZLGe
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for operating Feishu Docs, folders, and attachments, and sending notifications via custom bot webhooks. Enables AI assistants to automate document workflows in Feishu.
      1
      MIT

    • Remnus

      Ranork
      A
      license
      Not graded
      quality
      A
      maintenance
      Notion-like workspace of pages and customizable databases with a remote MCP server (OAuth 2.1 + PKCE, scoped read/write tokens, full audit log). 14 tools to search, read, and write pages, database rows, and database schemas.
      73
      AGPL 3.0

    • Feishu/Lark OpenAPI MCP

      KAIpany
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A tool designed to help users connect AI Agents with the Feishu/Lark platform, encapsulating Feishu/Lark Open Platform API interfaces as MCP tools for document processing, conversation management, calendar scheduling and more.
      7,520 npm
      -

    • Feishu/Lark OpenAPI MCP

      TestKAi005
      A
      license
      Not graded
      quality
      D
      maintenance
      This is the Feishu/Lark official OpenAPI MCP (Model Context Protocol) tool designed to help users quickly connect to the Feishu/Lark platform and enable efficient collaboration between AI Agents and Feishu/Lark. The tool encapsulates Feishu/Lark Open Platform API interfaces as MCP tools, allowing AI assistants to directly call these interfaces and implement various automation scenarios such as document processing, conversation management, calendar scheduling, and more.
      7,520 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are mostly distinct: docs (create, edit, get, read) vs smartsheets (add_records, get_fields, get_records, get_sheet, setup_fields). However, wecom_get_doc_content and wecom_read_doc overlap in purpose (both fetch content), though read auto-detects smartsheets, creating slight ambiguity.

    Naming Consistency4/5

    All tools follow wecom_verb_noun pattern, but verbs vary (create, edit, get, read, add, setup). Consistent snake_case and prefix, but 'get' vs 'read' for similar operations is a minor inconsistency.

    Tool Count5/5

    With 9 tools covering document and smartsheet operations, the count is well-scoped. Each tool serves a clear purpose without redundancy, appropriate for the domain.

    Completeness4/5

    Covers core CRUD for docs (create, edit, read) and smartsheets (schema, records, sheets). Missing delete/update for smartsheets or document deletion, but essential workflows are complete, so minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources