LENI, THE AI MANAGER

Leni, an AI agent, runs your
feedback board every day.

Collecting scattered feedback, merging duplicates, detecting releases to mark items done, drafting changelogs and notifications — connect GitHub once and Leni handles the rest.

Start free What Leni does →

claude — lenit-mcp

● Claude Code 1.4 · lenit-mcp connected

DAILY BY LENI

What Leni finishes before you clock in.

Every morning, Leni does a lap around your board and gets these done. You just review:

01Auto-collect feedback

“I filed 6 pieces of feedback from ChannelTalk, Slack and email yesterday.”

└ Runs daily · approval inbox

Extracts only feature requests and bug reports from support chats, and merges lookalikes into existing posts as votes. Low-confidence items go to the approval queue.

02Release detected → marked done

“I detected the v1.24 release and moved 'Dark mode support' to Done.”

└ Monitors GitHub commits & releases

Reads merged PRs and releases, finds the related feedback, and updates its status. Your roadmap stays current, hands-free.

03Changelog draft + notifications

“I drafted a changelog from this release. Publishing will notify all 47 participants.”

└ Drafts only — humans publish

Writes a draft from your changes and links the related feedback. The customer-facing publish button stays with a human.

ALREADY USING AI?

Already using an AI agent? Connect directly via MCP.

On top of what Leni automates, you can operate Lenit from Claude Code, Cursor, and Codex. Two minutes per tool — if it supports remote MCP, it works.

Claude Code

Connect remote MCP with one CLI line.

Cursor

Just add the URL to ~/.cursor/mcp.json.

Codex

Add it to ~/.codex/config.toml.

https://api.lenit.cloud/api/v1/mcp

WHY MCP

A simple protocol, the full product surface.

01

No install required.

Just one remote HTTP endpoint, https://api.lenit.cloud/api/v1/mcp. No local package, bridge, or SDK.

02

The full feature set.

Your agent does what you do in the dashboard — drafting changelogs, browsing feedback, and related search.

03

One browser login.

Add the URL to your client and a browser login opens to connect automatically. No copying tokens. (OAuth 2.1)

04

Any client.

Works with Claude Code, Cursor, Codex, and any client that supports remote MCP.

FAQ

Frequently asked questions.

Who is Leni?

Leni is the AI manager built into Lenit. It handles the repetitive work daily — collecting feedback, merging duplicates, detecting releases, marking items done, drafting changelogs, and sending notifications.

What do I need to do to use Leni?

Just connect GitHub. Leni runs daily after that, and low-confidence actions wait in an approval queue for your final call.

Can Leni publish on its own?

No. Customer-facing publishing is always done by a human. Leni only goes as far as drafts and suggestions, and every action is logged.

What is MCP?

Model Context Protocol — a standard for AI agents to talk to external tools. Lenit supports it, so the AI tools you already use can operate Lenit directly.

Does MCP require an install?

No. Just register the URL (api.lenit.cloud/api/v1/mcp) in your client and connect via browser login (OAuth 2.1).

How is it priced?

AI features are available on paid plans. See the pricing page for details.

Leave the board to Leni.

Start free