Inspiration

As developers, there is nothing more frustrating than a silent deployment failure. You push code, move on to the next task, and hours later realize your site is broken. Digging through massive CI/CD logs just to find a single syntax error is tedious and kills productivity. We wanted to bring the exact error directly to where the team communicates, transforming a messy log into an actionable alert.

What it does

LarkSentinel acts as a smart bridge between your deployment pipeline and your Lark workspace. When a build fails (e.g., on Netlify), the system catches the webhook. Instead of just sending a generic "Deploy Failed" text, it leverages Lark's Model Context Protocol (MCP) to analyze the context of the error, and instantly pushes a rich, interactive Message Card to your developer chat. You get the exact repository, the failing commit, and a snippet of the error log right in your workflow.

How we built it

The core backend is built in Python, acting as a lightweight server to listen for outgoing webhooks from GitHub and Netlify. Once the payload is received, we parse the JSON data to extract the specific error strings. The magic happens using the Lark Developer API and MCP, which takes that raw data, formats it into a highly readable UI component (Lark Message Cards), and routes it securely to the designated team channel.

Challenges we ran into

Parsing the complex JSON payloads from the deployment webhooks and isolating only the relevant error context without cluttering the chat was a significant challenge. Additionally, designing the Lark Message Cards to look clean, native, and actionable required iterating through Lark's UI builder.

What we learned

We learned how incredibly flexible Lark's MCP and developer tools are for building internal developer workflows. Connecting external CI/CD pipelines to a communication hub can be done elegantly with minimal overhead.

What's next for LarkSentinel

The next step is adding two-way communication: introducing interactive buttons inside the Lark chat that allow developers to instantly trigger a GitHub rollback or re-run a deployment without ever leaving the Lark app.

Built With

Share this project:

Updates