Sema

com.sema-langPublished by sema-lang.comv2.0.0Updated Oct 29, 2026

MCP tools for Sema — eval, compile, build, format, and docs for a Lisp with LLM primitives.

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

MCP server for Sema, a Lisp with LLM primitives, letting an assistant evaluate, compile, format, build and look up docs for Sema code.

What you can do
  • Evaluate and compile Sema Lisp expressions and scripts in the user's environment
  • Format Sema source and build standalone executables
  • Look up language and standard-library documentation
  • Call the user's own deftool Lisp tools defined in Sema
When to use it
Useful when working with Sema code or building LLM agent scripts in Sema and you want the assistant to run, format, build or document that code directly rather than guessing at an unfamiliar language.
Requirements
Runs as a local process on the user's machine (desktop only), distributed as an mcpb package; the README describes installing the Sema binary via installer script, Homebrew, crates.io or source build. No authentication, environment variables or headers are declared.
Before you install
Evaluating Sema code runs it locally, and the language includes shell, file write and HTTP functions, so code the assistant evaluates can modify files or run commands. Sema's LLM features read provider API keys from environment variables and can spend money against provider accounts; budget limits are available but optional.

Installation

In SourceWeft

  1. Open Sema in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Sema]

Sema

A Lisp where LLM agents are language primitives, not an SDK — compiled to a fast bytecode VM, shipped as a single binary.

[Playground] [Docs] [Version] [Coverage] [License]

Docs · Playground · For Agents · Examples · Issues

Stop rewriting the agent loop. Every LLM script grows the same scaffolding — retries, caching, cost caps, rate limits, tool dispatch, conversation state. Sema makes that scaffolding the runtime: your script stays the size of its idea, ships as a single binary, and your coding agent already speaks the language.

Sema is a Scheme-like Lisp where prompts are s-expressions, conversations are persistent data structures, and LLM calls are just another form of evaluation — with Clojure-style keywords (:foo), map literals ({:key val}), and vector literals ([1 2 3]).

What It Looks Like

A coding agent with file tools, safety checks, and budget tracking — in ~40 lines:

scheme
;; Define tools the LLM can call(deftool read-file  "Read a file's contents"  {:path {:type :string :description "File path"}}  (lambda (path)    (if (file/exists? path) (file/read path) "File not found")))
(deftool edit-file  "Replace text in a file"  {:path {:type :string} :old {:type :string} :new {:type :string}}  (lambda (path old new)    (file/write path (string/replace (file/read path) old new))    "Done"))
(deftool run-command  "Run a shell command"  {:command {:type :string :description "Shell command to run"}}  (lambda (command) (:stdout (shell "sh" "-c" command))))
;; Create an agent with tools, system prompt, and spending limit(defagent coder  {:system (format "You are a coding assistant. Working directory: ~a" (sys/cwd))   :tools [read-file edit-file run-command]   :max-turns 20})   ; no :model → uses the configured default provider
;; Run it — budget is scoped, automatically restored after the block(llm/with-budget {:max-cost-usd 0.50} (lambda ()  (define result (agent/run coder "Add error handling to src/main.rs"))  (println (:response result))  (println (format "Cost: $~a" (:spent (llm/budget-remaining))))))

Key Features

scheme
;; Simple completion(llm/complete "Explain monads in one sentence")
;; Structured data extraction — returns a map, not a string(llm/extract  {:vendor {:type :string} :amount {:type :number} :date {:type :string}}  "Bought coffee for $4.50 at Blue Bottle on Jan 15");; => {:amount 4.5 :date "2025-01-15" :vendor "Blue Bottle"}
;; Classification(llm/classify (list :positive :negative :neutral) "This product is amazing!");; => :positive
;; Multi-turn conversations as immutable data(define conv (conversation/new {:model "claude-haiku-4-5-20251001"}))(define conv (conversation/say conv "The secret number is 7"))(define conv (conversation/say conv "What's the secret number?"))(conversation/last-reply conv) ;; => "The secret number is 7."
;; Streaming(llm/stream "Tell me a story" {:max-tokens 500})
;; Batch — all prompts sent concurrently(llm/batch (list "Translate 'hello' to French"                 "Translate 'hello' to Spanish"                 "Translate 'hello' to German"))
;; Vision — extract structured data from images(llm/extract-from-image  {:text :string :background_color :string}  "assets/logo.png");; => {:background_color "white" :text "Sema"}
;; Multi-modal chat — send images in messages(define img (file/read-bytes "photo.jpg"))(llm/chat (list (message/with-image :user "Describe this image." img)))
;; Cost tracking(llm/set-budget 1.00)(llm/budget-remaining) ;; => {:limit 1.0 :spent 0.05 :remaining 0.95}
;; Response caching — avoid duplicate API calls during development(llm/with-cache (lambda ()  (llm/complete "Explain monads")))
;; Cassettes — record real responses once, replay them in CI (no keys, no network)(llm/with-cassette "fixtures/run.jsonl" {:mode :auto} (lambda ()  (llm/complete "Explain monads")))
;; Fallback chains — automatic provider failover(llm/with-fallback [:anthropic :openai :groq]  (lambda () (llm/complete "Hello")))
;; In-memory vector store for semantic search (RAG)(vector-store/create "docs")(vector-store/add "docs" "id" (llm/embed "text") {:source "file.txt"})(vector-store/search "docs" (llm/embed "query") 5)
;; Cross-encoder reranking — the retrieve-many → rerank-to-a-few RAG move(llm/rerank "how do I read a file?"            ["file/read returns a string" "http/get fetches a URL"]            {:top-k 3});; => ({:index 0 :score 0.98 :document "file/read returns a string"} ...)
;; Text chunking for LLM pipelines(text/chunk long-document {:size 500 :overlap 100})
;; Prompt templates(prompt/render "Hello {{name}}" {:name "Alice"}); => "Hello Alice"
;; Persistent key-value store(kv/open "cache" "cache.json")(kv/set "cache" "key" {:data "value"})(kv/get "cache" "key")

Supported Providers

All providers are auto-configured from environment variables — just set the API key and go.

ProviderChatStreamToolsEmbeddingsVision
Anthropic✅✅✅—✅
OpenAI✅✅✅✅✅
Google Gemini✅✅✅—✅
Ollama✅✅✅—✅
Groq✅✅✅——
xAI✅✅✅——
Mistral✅✅✅——
Moonshot✅✅✅——
Jina———✅—
Voyage———✅—
Cohere———✅—
Any OpenAI-compat✅✅✅—✅
Custom (Lisp)✅—✅——

It's Also a Real Lisp

Hundreds of built-in functions, tail-call optimization, macros, modules, error handling — not a toy.

scheme
;; Closures, higher-order functions, TCO(define (fibonacci n)  (let loop ((i 0) (a 0) (b 1))    (if (= i n) a (loop (+ i 1) b (+ a b)))))(fibonacci 50) ;; => 12586269025
;; Full R7RS numeric tower — bignums, exact rationals, complex numbers(expt 2 100)   ;; => 1267650600228229401496703205376(+ 1/2 1/3)    ;; => 5/6(sqrt -1)      ;; => 0+1i
;; Maps, keywords-as-functions, f-strings(define person {:name "Ada" :age 36 :langs ["Lisp" "Rust"]})(:name person) ;; => "Ada"(println f"${(:name person)} knows ${(length (:langs person))} languages")
;; Destructuring(let (({:keys [name age]} person))  (println f"${name} is ${age}"))
;; Pattern matching with guards(define (classify n)  (match n    (x when (> x 100) "big")    (x when (> x 0)   "small")    (_                 "non-positive")))
;; Functional pipelines(->> (range 1 100)     (filter even?)     (map #(* % %))     (take 5));; => (4 16 36 64 100)
;; Nested data access(define config {:db {:host "localhost" :port 5432}})(get-in config [:db :host])  ;; => "localhost"
;; Macros(defmacro unless (test . body)  `(if ,test nil (begin ,@body)))
;; Modules(module utils (export square)  (define (square x) (* x x)))
;; HTTP, JSON, regex, file I/O, crypto, CSV, datetime...(define data (json/decode (http/get "https://api.example.com/data")))

📖 Full language reference, stdlib docs, and more examples at sema-lang.com/docs

Try It Now

sema.run — Browser-based playground with 20+ example programs. No install required. Runs entirely in WebAssembly.

Teach Your Coding Agent Sema in One Line

Sema is new, so your agent hasn't seen it. Fix that in one command — append the agent crib sheet to your repo's AGENTS.md (and point CLAUDE.md at it):

bash
curl -fsSL https://sema-lang.com/docs/for-agents.md >> AGENTS.mdln -s AGENTS.md CLAUDE.md     # Claude Code, Cursor, etc. read this

for-agents.md is a compact working guide for an LLM that already knows a Lisp. It covers the rules most likely to cause incorrect generated code and links to /llms.txt, a machine index of every doc page. The agent can fetch only the page it needs (for example, /docs/llm/tools-agents.md) instead of loading the whole manual. Every doc URL also serves raw Markdown: append .md to a sema-lang.com/docs/... link to get the source.

Installation

Install pre-built binaries (no Rust required):

bash
# macOS / Linuxcurl -fsSL https://sema-lang.com/install.sh | sh
# Windows (PowerShell)powershell -ExecutionPolicy ByPass -c "irm https://github.com/sema-lisp/sema/releases/latest/download/sema-lang-installer.ps1 | iex"
# Homebrew (macOS / Linux)brew install helgesverre/tap/sema-lang

Or install from crates.io:

bash
cargo install sema-lang

Or build from source:

bash
git clone https://github.com/sema-lisp/semacd sema && cargo build --release# Binary at target/release/sema

For local development that needs an optimized binary, use jake release-fast or cargo build --profile release-fast. The binary is at target/release-fast/sema. This profile uses incremental compilation and parallel codegen, with no cross-crate LTO. Use --release for performance measurements and distribution builds. See the build profile measurements for build times and runtime tradeoffs.

bash
sema                          # REPL (with tab completion)sema script.sema              # Run a filesema -e '(+ 1 2)'             # Evaluate expressionsema --no-llm script.sema     # Run without LLM (faster startup)sema build app.sema -o myapp  # Build standalone executable./myapp                       # Run without sema installed

Shell Completions

Generate tab-completion scripts for your shell:

bash
# Zsh (macOS / Linux)mkdir -p ~/.zsh/completionssema completions zsh > ~/.zsh/completions/_sema
# Bashmkdir -p ~/.local/share/bash-completion/completionssema completions bash > ~/.local/share/bash-completion/completions/sema
# Fishsema completions fish > ~/.config/fish/completions/sema.fish

📖 Full setup instructions for all shells: sema-lang.com/docs/shell-completions

📖 Full CLI reference, flags, and REPL commands: sema-lang.com/docs/cli

Editor Support

Each editor plugin lives in its own repo under the sema-lisp org:

EditorRepositoryInstall
VS Codevscode-semaext install sema-lang.sema-lang
Zedzed-semaExtensions → search Sema
IntelliJintellij-semaJetBrains Marketplace → Sema
Neovimsema.nvim{ "sema-lisp/sema.nvim" }
Vimsema.vimPlug 'sema-lisp/sema.vim'
Emacsemacs-semaMELPA → sema-mode
Helixhelix-semaclone + ./install.sh
Sublime Textsublime-semaPackage Control → Sema

All plugins provide syntax highlighting; VS Code, Zed, IntelliJ, Neovim, Emacs, Helix, and Sublime also wire up the built-in language server (sema lsp), and several (VS Code, Zed, IntelliJ, Neovim, Helix) add debugging (sema dap) — some also register the MCP server (sema mcp). Zed, Helix, and Neovim highlight via the shared tree-sitter-sema grammar; the others ship their own.

📖 Full installation instructions and per-editor feature lists: sema-lang.com/docs/editors

Notebook

Sema includes a Jupyter-inspired notebook interface with a browser UI:

bash
sema notebook new my-notebook.sema-nb        # Create a notebooksema notebook serve my-notebook.sema-nb      # Open in browser (localhost:8888)sema notebook run my-notebook.sema-nb        # Run all cells headlesslysema notebook export my-notebook.sema-nb     # Export to Markdown

Cells share a persistent environment — definitions in earlier cells are visible in later ones. Notebooks are saved as .sema-nb JSON files.

📖 Full notebook documentation: sema-lang.com/docs/notebook

Language Tooling

A full toolchain ships in the box — no plugins to assemble:

bash
sema fmt script.sema     # Canonical code formattersema lsp                 # Language Server (completions, hover, go-to-def, rename)sema dap                 # Debug Adapter (breakpoints, stepping, variable inspection)sema mcp                 # Model Context Protocol server for LLM clients

The MCP server lets LLM clients (Claude Desktop, Cursor, Claude Code) compile, format, evaluate, and build Sema code — and call your own deftool Lisp tools — directly in your environment.

📖 Formatter · LSP · Debugger · MCP

Example Programs

The examples/ directory has 50+ programs:

ExampleWhat it does
coding-agent.semaFull coding agent with file editing, search, and shell tools
review.semaAI code reviewer for git diffs
commit-msg.semaGenerate conventional commit messages from staged changes
summarize.semaSummarize files or piped input
game-of-life.semaConway's Game of Life
brainfuck.semaBrainfuck interpreter
mandelbrot.semaASCII Mandelbrot set
json-api.semaFetch and process JSON APIs
test-vision.semaVision extraction and multi-modal chat tests
test-extract.semaStructured extraction and classification
test-batch.semaBatch/parallel LLM completions
test-pipeline.semaCaching, budgets, rate limiting, retry, fallback chains
test-text-tools.semaText chunking, prompt templates, document abstraction
test-vector-store.semaIn-memory vector store with similarity search
test-kv-store.semaPersistent JSON-backed key-value store
expr-evaluator.semaMini calculator using match on tagged vectors
shape-geometry.semaShape areas/perimeters with map pattern matching
http-router.semaHTTP router with match on nested maps and guards
destructuring.semaComprehensive destructuring showcase (vector, map, lambda)
demo.sema-nbInteractive notebook demo (run with sema notebook serve)

Why Sema?

The pitch in one line: no LangChain, no provider SDK, no agent framework, no glue script — the agent loop, retries, caching, budgets, tracing, and tool dispatch are the language runtime, and the whole thing is one binary you can scp to a box.

  • LLMs as language primitives — prompts, messages, conversations, tools, and agents are first-class data types, not string templates bolted on
  • Multi-provider — swap between Anthropic, OpenAI, Gemini, Ollama, any OpenAI-compatible endpoint, or define your own provider in Sema
  • Pipeline-ready — response caching, fallback chains, rate limiting, retry with backoff, text chunking, prompt templates, vector store, and a persistent KV store
  • Cost-aware — built-in budget tracking with a bundled pricing snapshot (models.dev), updated per release
  • Observable — every LLM/agent run is auto-traced with OpenTelemetry (GenAI semantic conventions): tokens, cost, latency, and the full invoke_agent → chat → execute_tool tree, exportable to Jaeger, Grafana, Datadog, Langfuse, Arize Phoenix, and more — zero manual instrumentation, off by default
  • Practical Lisp — closures, TCO, macros, modules, error handling, HTTP, file I/O, regex, JSON, and a comprehensive stdlib
  • Standalone executables — sema build compiles programs into self-contained binaries with auto-traced imports and bundled assets
  • Embeddable — a Rust crate with a builder API, or @sema-lang/sema to run Sema client-side in JS via WebAssembly
  • Full toolchain — formatter, language server (LSP), debugger (DAP), and an MCP server for LLM clients, all built in
  • Package manager — sema pkg pulls dependencies from git or the live registry at pkg.sema-lang.com, pinned by a sema.lock for reproducible installs
  • Developer-friendly — REPL with tab completion, structured error messages with hints, and 50+ example programs

Why Not Sema?

  • No continuations (call/cc) or fully hygienic macros (syntax-rules) — has auto-gensym (foo#) for preventing variable capture
  • Single-threaded — Rc-based, no cross-thread sharing of values
  • No JIT — bytecode compiler + stack-based VM, no native code generation
  • Young language — solid but not battle-tested at scale

Architecture

crates/  sema-core/     NaN-boxed Value type, errors, environment  sema-reader/   Lexer and s-expression parser  sema-vm/       Bytecode compiler and virtual machine  sema-eval/     Trampoline-based evaluator, special forms, modules  sema-stdlib/   Built-in functions across many modules  sema-io/       Process-wide async I/O pool (tokio) behind the core seam  sema-llm/      LLM provider trait + multi-provider clients  sema-workflow/ Dynamic-workflow runtime — journaled runs, bounded fan-out, --resume  sema-otel/     OpenTelemetry tracing (GenAI semantic conventions)  sema-docs/     Canonical builtin docs (powers LSP hover + REPL apropos)  sema-lsp/      Language Server Protocol implementation  sema-dap/      Debug Adapter Protocol server  sema-fmt/      Source code formatter  sema-mcp/      Model Context Protocol server  sema-notebook/ Jupyter-inspired notebook interface with browser UI  sema-wasm/     WebAssembly build for sema.run playground  sema/          CLI binary: REPL + file runner + standalone builder

🔬 Deep-dive into the internals: Architecture · Evaluator · Lisp Comparison

License

MIT — see LICENSE.

Source: README.md at commit 3b1e81b

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

4
  1. v2.0.0LatestOct 29, 2026
  2. v1.37.0Oct 9, 2026
  3. v1.36.1Oct 5, 2026
  4. v1.36.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts