Lema MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 56 installs a week from npm. Last commit 31 Jul 2026.
Cited 'why was this decided?' answers for your repo and for React, Kubernetes, and Rust.
We read the source, 12 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const result = spawnSync(binPath, process.argv.slice(2), { stdio: 'inherit' });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return filepath.Join(root, path)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add lema-mcp -- npx -y lema-mcp
{
"mcpServers": {
"lema-mcp": {
"args": [
"-y",
"lema-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.lema-mcp]
command = "npx"
args = ["-y", "lema-mcp"]
{
"mcpServers": {
"lema-mcp": {
"args": [
"-y",
"lema-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"lema-mcp": {
"args": [
"-y",
"lema-mcp"
],
"command": "npx"
}
}
}
Decision provenance for AI-coded codebases: the why, and what was already tried and rejected.
Website traffic, bot reports, realtime visitors and site health for your DevDome sites
Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.
13 rules that decide whether a vulnerability report ever reaches you
Catches files and C# members you forgot to change, learned from your repo's git history
Self-reported attribution: which channel and which creator your users first heard you from.
Deterministic context layer for your codebase: change impact, blast radius, answers with receipts.
Ask a repository what depends on what. Every answer cites the file, line and commit it came from.
Answers built from our own checks of this server.