Testing Feishu/Lark MCP Servers

Feishu and Lark workflows often put documents, approvals, project data, and internal knowledge behind MCP servers. MCP Observatory helps teams test those servers before agents depend on them.

Local Server Check

npx @kryptosai/mcp-observatory test --security npx -y feishu-doc-mcp

Use --security when the server exposes document search, write actions, internal URLs, or credential-backed tools.

Internal HTTP MCP Check

For an internal HTTP MCP endpoint, create a target file:

{
  "targetId": "feishu-doc-mcp",
  "adapter": "http",
  "url": "https://internal.example.com/mcp",
  "authToken": "${FEISHU_MCP_TOKEN}",
  "timeoutMs": 30000
}

Then run:

export FEISHU_MCP_TOKEN="..."
npx @kryptosai/mcp-observatory test --target feishu-target.json --security

CI Report

name: Feishu MCP Check
on: [pull_request]

jobs:
  observatory:
    runs-on: ubuntu-latest
    env:
      MCP_OBSERVATORY_ORG: your-company.com
      MCP_OBSERVATORY_CONTACT: your-team-contact
    steps:
      - uses: actions/checkout@v4
      - uses: KryptosAI/mcp-observatory/action@v1.28.0
        with:
          target: feishu-target.json
          security: true

Enterprise Report

npx @kryptosai/mcp-observatory enterprise-report \
  --account "Feishu MCP production fleet" \
  --format html \
  --output feishu-mcp-report.html

Production teams can use the report for MCP owner reviews, private-repo CI history, security review, and certification conversations.

Open a pilot request from the GitHub issue chooser for production Feishu/Lark MCP usage, hosted reporting, private deployment, or fleet visibility.

FilesExpand file tree

feishu-lark-mcp.md

Latest commit

History