Lemma MCP server
Commit Nov 15, 2026Enables teams to build and share AI agents, web apps, and automated workflows that integrate with Slack, WhatsApp, and other communication surfaces.
Also known as lemma-work/lemma-platform
- Stars
- 651
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 15, 2026
- License
- AGPL-3.0
What is Lemma MCP?
Lemma enables teams to build and share AI agents, web apps, and automated workflows that integrate with Slack, WhatsApp, and other communication surfaces.
Summary generated from the project's README
About Lemma MCP server
Lemma provides a multiplayer environment for teams to create and deploy AI agents, web applications, and automated workflows. It functions as a digital teammate that can be shared across an organization, operating within a secure boundary called a pod. Users can deploy the platform via Lemma Cloud, run it locally on macOS, or self-host the entire stack on a private server using Docker and HTTPS.
Integration is a core feature, allowing agents to interact through surfaces like Slack, WhatsApp, Microsoft Teams, Telegram, and email. The system supports various model providers, including existing Claude Code or Codex subscriptions, hosted models from Lemma, or any OpenAI and Anthropic compatible API keys. Developers can build custom interfaces using a TypeScript SDK and manage complex processes through durable workflows that include human-in-the-loop approvals for consequential actions.
This platform distinguishes itself by combining structured data in tables with unstructured memory in Markdown notes. It allows for granular permission models where both people and agents are subject to the same row-level security and access controls.
What you can do with it
- 1Automate repetitive team tasksA developer can instruct an AI client to build a teammate that manages specific jobs, tables, and workflows based on existing team context.
- 2Deploy custom web interfacesYou can request the creation of a web app with its own URL to manage queues, boards, or forms that interact with agent data.
- 3Manage human-in-the-loop approvalsConfigure agents to pause and request permission before performing sensitive operations like issuing refunds or deleting records.
- 4Sync work across communication toolsEnable your team to interact with AI agents directly through their preferred chat applications like Slack or WhatsApp.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablelemma-work/lemma-platform is public and reachablegithub.com/lemma-work/lemma-platform ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/lemma-work/lemma-platform ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubLemma
A multiplayer harness that shapes itself around your work.
Your people meet it as a teammate: give it a job, share it with everyone, and teach it as you go.
It runs on the Claude Code or Codex subscription you already pay for, Lemma's hosted models, or any OpenAI- or Anthropic-compatible key.
Get started
Lemma Cloud. Sign up at lemma.work. Nothing to install.
On your Mac. Download Lemma, open it, and choose Local. It installs everything it needs and runs on your machine. See installation if something doesn't start.
On your own server. Bring up the whole stack on a VM you control, with HTTPS. See self-hosting.
git clone https://github.com/lemma-work/lemma-platform.git
cd lemma-platform/deploy/compose && ./bootstrap.sh
# add your model provider key to .env, then:
docker compose up -d
Your coding agent. Claude Code, Codex, Cursor, OpenCode or Antigravity can build a whole teammate. Paste this in:
Set up Lemma, then build me a teammate.
1. Install the CLI with `uv tool install lemma-terminal` (not pip; it needs
Python 3.14 and uv provides it).
2. Run `lemma auth login` and let me finish signing in.
3. Run `lemma skills install`, then tell me to restart you so the skills load.
4. After the restart, use the Lemma builder skills.
Based on what you already know about me, my work and how my team works,
propose the one teammate that would take the most off our plate: its job,
who it works with, and what it should never do without asking. Ask me
anything you can't work out. Once I agree, build it: the tables that hold
the shared state, the agents and workflows that move the work, the app
people open, and the permissions, with a person approving anything
consequential.
It writes everything as files, imports them, and runs the workflow to check it stops where it should.
Inside a teammate
Each teammate lives in a pod: the boundary around one job. A pod holds its own agents, apps, tables, files and workflows, decides who is inside and what each person and agent can touch, and nothing crosses it unless you connect it. It exports as a folder of files, so you can version it, share it, or import it somewhere else.
Agents
An agent is a role: a model, an instruction, and the tools, tables and connectors it is allowed to use. It answers when someone asks, and it also runs without being asked, on a schedule, when a row in a table changes, or when a webhook arrives from Slack, GitHub or anywhere else. Each run is recorded step by step, so you can see what it read, what it called, and where it stopped.
Before anything consequential, like sending an email, issuing a refund or deleting a record, it pauses and asks the person who owns that decision. The run waits, for days if it has to, and carries on when they answer.
Apps
A lot of work needs a screen rather than a chat thread: a queue to clear, a board to move, a form to fill in. Ask the teammate for one and it builds a web app, deployed at its own URL, that reads and writes the same tables its agents use. When an agent updates a record, the app is already showing it.
Apps are built on the TypeScript SDK, so a developer can open the code, change
it, and redeploy with lemma apps deploy.
People
A teammate is shared by the whole team, and each person has their own account and role inside it. One permission model covers people and agents alike: which tables they can read or write, which rows they can see, and which steps need their approval. Clients and guests are invited the same way and see only their part.
Every action lands in one history: who asked, which agent ran, and what changed.
Context
The teammate keeps its memory as Markdown notes. Shared notes are readable by everyone on the team; personal notes only by you. Correct it once ("refunds over $500 go to Sam") and it writes that down and works that way from then on. Any note can be opened, read and fixed by hand.
Alongside the notes are tables, typed records with row-level security, and files, the documents and PDFs agents can search. All three are read at run time, so what the teammate knows is what your team can see and edit.
Surfaces
People reach the same teammate from Slack, Microsoft Teams, WhatsApp, Telegram and email. Each surface works out who is writing, matches them to their account, and applies their permissions, so a question in a Slack thread gets the same answer it would get in the app. Every agent also has its own email address that anyone can write to.
Approvals travel too: a workflow waiting on someone can ask them in the chat they already use.
Workflows
When work passes between people and agents in the same order every time, write it down as a workflow. Each step is an agent, a function (plain code that does the same thing every time), a decision, a loop, a wait, or a form for a named person. A workflow starts on a schedule, a table change, a webhook, or by hand.
Runs are durable. A step waiting on a person can wait for days, and the run resumes exactly where it stopped.
Open source
The core is AGPLv3; the SDKs, CLI and skills are Apache-2.0. Run it on your laptop, your own server, or Lemma Cloud. To work on Lemma itself, start with CONTRIBUTING.md and ARCHITECTURE.md.
Questions go in Discussions or Discord.
© 2026 Folks and Machines, Inc.
Lemma MCP questions
How can I run Lemma on my own infrastructure?
You can self-host the entire stack on a VM you control using Docker Compose.
What model providers can I use with Lemma?
Lemma works with Claude Code, Codex subscriptions, Lemma's hosted models, or any OpenAI- or Anthropic-compatible API key.
Can I use Lemma with my existing chat tools?
Yes, people can interact with teammates through Slack, Microsoft Teams, WhatsApp, Telegram, and email.
How does Lemma handle sensitive actions?
The system can pause workflows to ask for human approval before performing consequential actions like sending emails or deleting records.