Mort Mcp

io.github.0xmortuexPublished by GitHub account 0xmortuexv0.1.0Updated Oct 27, 2026

Write, type-check and run Mort code, with language spec and stdlib lookup.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Lets an assistant write, type-check, run and format Mort, a statically typed systems language, with spec and stdlib lookup.

What you can do
  • Type-check Mort source text or files and get file:line:col diagnostics
  • Compile and run programs with stdin, args and a timeout, reporting output and exit code
  • Inspect generated C output, including freestanding kernel-mode output
  • Format code with the official formatter
  • List std modules or show a module's exact signatures, struct fields and doc comments
  • Search the language spec and reference docs, and list or read example programs
When to use it
Useful when an assistant must write or debug Mort code, a language unlikely to be in model training data, and would otherwise guess Rust-like syntax. Also handy for checking compiler and language version or looking up stdlib signatures.
Requirements
Runs locally over stdio as the PyPI package mort-mcp. Needs the Mort compiler: either a checkout of the Mort repository pointed to by the MORT_HOME environment variable, or a mortc binary on PATH. The ziglang package provides a zero-install C backend for running programs; docs and examples tools require the checkout.
Before you install
mort_run compiles and executes arbitrary Mort code on your machine, so only run code you trust. The optional MORT_HOME checkout is read for docs and examples. No authentication or API keys are declared.

Installation

In SourceWeft

  1. Open Mort Mcp 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

mort-mcp

Let an AI agent write a language it has never seen.

Mort is a statically typed systems language that compiles to C. It's the language MORT OS is written in. No model has Mort in its training data, so an agent asked to write it will guess Rust-like syntax and get it wrong.

mort-mcp gives the agent what a human newcomer would use: a fast type checker with precise errors, a way to run programs, the language spec to search, and the exact signatures of the standard library.

> mort_checkFAILED:error: <source>:4:1: argument 1 of 'strings.starts_with' expects []const u8, got *u8        if strings.starts_with("mortos", "mort") {
> mort_std strings// First byte offset of `needle` in `text`, or None if it does not occur.pub fn index_of(text: []const u8, needle: []const u8) -> Option<u64>;...
> mort_run[exit 0]1

Install

You need the Mort compiler. The simplest setup is a checkout, which also brings the docs and examples:

bash
git clone https://github.com/0xmortuex/Mortpip install mort-mcp ziglang     # ziglang = zero-install C backend for mort_runclaude mcp add mort --env MORT_HOME=/path/to/Mort -- mort-mcp

Without MORT_HOME, mort-mcp uses a mortc on your PATH (pip install git+https://github.com/0xmortuex/Mort). Checking, running and std lookup all work that way. mort_docs and mort_examples need the checkout.

Tools

ToolWhat it does
mort_checkType-check source text or files without building. Fast, and needs no C compiler. Returns diagnostics as file:line:col with the source line.
mort_runCompile and run, with stdin, args and a timeout. Reports output and exit code.
mort_emit_cShow the generated C. freestanding=True shows the kernel-mode output.
mort_formatFormat with the official formatter (mortc fmt).
mort_stdList std modules, or show one module's public API: exact signatures, struct fields and doc comments.
mort_docsSearch the language specification and reference docs, e.g. "resource struct cleanup" or "integer overflow".
mort_examplesList or read the compiler's example programs.
mort_versionCompiler and language version, and where the compiler was found.

Every tool calls mortc through its command-line interface, and reads std signatures and docs from the installed compiler. Answers therefore match the version you're running, even as the language changes.

Tests

bash
pip install ".[test]" "ruff==0.16.0" "mypy==2.3.0" ziglangruff check src tests && mypy --strict srcMORT_HOME=/path/to/Mort pytest tests

Without MORT_HOME, only the unit tests and the MCP handshake test run. CI checks out the latest Mort and also runs every night, so a change to the compiler's CLI or docs layout shows up as a failing build.

License

MIT

Source: README.md at commit 4eb9965

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 11, 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