Skip to main content
Glama
axunrun

feishu-cli-mcp

by axunrun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to feishu-cli-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-cli-catalog

      abcpro1
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      7 npm
      1
      MIT

    • Portage

      jayaprakash2207
      A
      license
      Not graded
      quality
      A
      maintenance
      Turns any command-line tool into an MCP server by parsing its --help, enabling AI assistants to discover and safely invoke CLI tools with validation, allow-listing, and sandboxing.
      MIT

    • wrapmcp

      SubZtep
      A
      license
      Not graded
      quality
      C
      maintenance
      Universal MCP server that wraps any CLI tool, enabling AI assistants to run commands via natural language.
      1
      MIT

    • mcp-cli-gemini

      rlaksana
      F
      license
      A
      quality
      D
      maintenance
      Wraps the Gemini CLI as an MCP server, enabling AI tools to perform Gemini queries, interactive sessions, and extension management via a unified tool.
      1
      1
      -

    • Balena MCP

      kieksme
      A
      license
      B
      quality
      A
      maintenance
      Enables managing Balena fleets, devices, releases, variables, tags, teams, and organizations from MCP clients, locally over stdio or remotely over Streamable HTTP.
      41
      GPL 3.0
    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

    A4.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: running CLI commands, inspecting schemas, reading help, and checking auth status. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tools follow the consistent pattern 'lark_cli_' followed by a descriptive action (run, schema, help, auth_status). Perfectly uniform naming convention.

    Tool Count5/5

    Four tools is well-scoped for a CLI wrapper server, providing essential operations without unnecessary bloat. Each tool earns its place.

    Completeness4/5

    The surface covers running, schema lookup, help, and auth status, which are the core needs for interacting with lark-cli. A minor gap is lack of explicit logout or config tools, but these are workable via lark_cli_run with appropriate arguments.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources