Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Verifiable provenance for AI agents — ZK proofs over confidential documents, no plaintext exposure.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
LEMMA_API_KEY, LEMMA_API_BASE, AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"lemmaoracle": {
"command": "npx",
"args": [
"-y",
"@lemmaoracle/mcp"
],
"env": {
"LEMMA_API_KEY": "your-value",
"LEMMA_API_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add --transport http lemmaoracle https://mcp.lemma.workers.dev/mcp --header 'Authorization: your-value'claude mcp add lemmaoracle --env LEMMA_API_KEY=your-value --env LEMMA_API_BASE=your-value -- npx -y @lemmaoracle/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lemmaoracle": {
"url": "https://mcp.lemma.workers.dev/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"lemmaoracle": {
"command": "npx",
"args": [
"-y",
"@lemmaoracle/mcp"
],
"env": {
"LEMMA_API_KEY": "your-value",
"LEMMA_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"lemmaoracle": {
"type": "http",
"url": "https://mcp.lemma.workers.dev/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"lemmaoracle": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@lemmaoracle/mcp"
],
"env": {
"LEMMA_API_KEY": "your-value",
"LEMMA_API_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
LEMMA_API_BASE envAuthorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account lemmaoracle, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LEMMA_API_KEY, Authorization
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.0.17) reached the registry 6 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
@lemmaoracle/mcp@lemmaoracle/mcp is the Model Context Protocol (MCP) server that gives AI agents access to Lemma's verifiable provenance layer — query cryptographically verified attributes (zero-knowledge proofs, selective disclosure, tamper-evident provenance) from confidential documents without ever exposing the plaintext.
Models change. Proofs remain.
This is an MCP server. MCP (Model Context Protocol) is the open protocol for connecting AI agents to external tools and data sources, originally released by Anthropic and now maintained as a community standard. This package implements an MCP server using the official MCP SDK (@modelcontextprotocol/sdk) and exposes a set of read-only tools for querying Lemma's verifiable attribute API.
The current MVP exposes 5 read tools. Resources and prompts are not exposed in v0.0.x; write tools (register_document, submit_proof) are planned for Phase 2.
Two ways to connect — pick whichever matches your agent setup.
npx -y smithery mcp add lemmaoracle/lemma
Smithery proxies to the Lemma MCP endpoint at https://lemma--lemmaoracle.run.tools and prompts for your Lemma API key. Best for trying the server quickly or for agents that already speak Smithery. Server page: smithery.ai/servers/lemmaoracle/lemma.
Add this to your Claude Desktop MCP config:
{
"mcpServers": { "lemma": { "command": "npx", "args": ["-y", "@lemmaoracle/mcp"], "env": { "LEMMA_API_KEY": "YOUR_API_KEY" } } } }
Get an API key at https://lemma.frame00.com/services. LEMMA_API_BASE can be omitted (defaults to production endpoint).
When trying this server in Glama's in-browser inspector (or any MCP inspector), you can use the demo key below. It is read-only and scoped to demo data (the same key is used by example-x402):
LEMMA_API_KEY=b6363aa6265322ed0d786a11d5b6d3264947052ca72deba4cbe1685d099af892
LEMMA_API_BASE=https://workers.lemma.workers.dev
For production access, request a key at https://lemma.frame00.com/services.
This server exposes the following MCP tools (no resources or prompts in the current MVP):
| Tool | Phase | Description |
|---|---|---|
lemma_query_verified_attributes | MVP | Query cryptographically verified attributes from Lemma. Use this as the primary entry point for finding documents whose attributes match given conditions. |
lemma_get_schema | MVP | Retrieve a Lemma schema (attribute structure) by ID. |
lemma_get_circuit | MVP | Retrieve a ZK proof circuit (constraints + verifier) by ID. |
lemma_get_generator | MVP | Retrieve a document generator (input/output spec) by ID. |
lemma_get_proof_status | MVP | Get the verification status of a proof by its verificationId. |
lemma_register_document | Phase 2 | Register a new document on Lemma. |
lemma_submit_proof | Phase 2 | Submit a ZK proof for verification. |
@modelcontextprotocol/sdk (≥ 1.29).Lemma is designed so that we never receive plaintext documents. The MCP server only transmits commitments, hashes, and ZK proofs to the Lemma API. See https://lemma.frame00.com/privacy for the full privacy policy.
For contributors hacking on the MCP server itself, run it from a local build of this monorepo. End users should use the npx config above.
git clone https://github.com/lemmaoracle/lemma.git
cd lemma pnpm install pnpm -F @lemmaoracle/mcp build
The bin entry produces packages/mcp/dist/index.js. Point Claude Desktop at the absolute path:
{
"mcpServers": { "lemma": { "command": "node", "args": ["/absolute/path/to/lemma/packages/mcp/dist/index.js"], "env": { "LEMMA_API_KEY": "YOUR_API_KEY" } } } }
Rebuild after changes with pnpm -F @lemmaoracle/mcp build and restart Claude Desktop to reconnect. To point at a non-production API, add "LEMMA_API_BASE": "https://..." to env.
🇯🇵 日本語版はこちら / Japanese README