Lema MCP Server

Lema MCP server exists for a simple reason — assistants are far more useful when they can act on Lema directly instead of describing what you should do. Cited 'why was this decided?' answers for your repo and for React, Kubernetes, and Rust.

What you get

A local MCP server. No account, no database, no network for your own repo — install it in 30 seconds and ask why a project decided something, or whether the approach you're about to take was already rejected.

• Abstain ≠ approval. — Silence is reported as silence. lema would rather say
• Cited, summarized — not quoted. — Answers are grounded in recorded decisions and
• Local-first. — Capture and enforcement run entirely on your machine, in a file
• No fabricated graph. — A cold import writes no decision→decision edges and no

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 6 environment variables: LEMA_MCP_MODE, LEMA_PUBLIC_REPO, LEMA_API_URL, LEMA_API_TOKEN, LEMA_WORKSPACE_ID, GITHUB_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the lema mcp server does with a few real requests.

Choosing this one

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by lemahq; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.