GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Mort MCP
Overview
Description from the maker (original English)
Write, type-check and run Mort code, with language spec and stdlib lookup.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 26/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
MORT_HOME
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mort": {
"command": "uvx",
"args": [
"mort-mcp"
],
"env": {
"MORT_HOME": "your-value"
}
}
}
}Run this in your terminal
claude mcp add mort --env MORT_HOME=your-value -- uvx mort-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mort": {
"command": "uvx",
"args": [
"mort-mcp"
],
"env": {
"MORT_HOME": "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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"mort": {
"type": "stdio",
"command": "uvx",
"args": [
"mort-mcp"
],
"env": {
"MORT_HOME": "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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
MORT_HOMEenvPath to a checkout of github.com/0xmortuex/Mort (enables docs and examples)
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 10, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account 0xmortuex, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 5693 servers in this category
- Published to the registry more recently than 51% of the other 5693 servers in this category
- Basic checks equal to or better than 100% of the other 5693 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Mort MCP safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 30 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
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.
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: :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 ; ...
mort_run
[exit 0] 1
Install
You need the Mort compiler. The simplest setup is a checkout, which also brings the docs and examples:
git clone https://github.com/0xmortuex/Mortpip install mort-mcp ziglang # ziglang = zero-install C backend for mort_run claude 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
| Tool | What it does |
|---|---|
mort_check | Type-check source text or files without building. Fast, and needs no C compiler. Returns diagnostics as file:line:col with the source line. |
mort_run | Compile and run, with stdin, args and a timeout. Reports output and exit code. |
mort_emit_c | Show the generated C. freestanding=True shows the kernel-mode output. |
mort_format | Format with the official formatter (mortc fmt). |
mort_std | List std modules, or show one module's public API: exact signatures, struct fields and doc comments. |
mort_docs | Search the language specification and reference docs, e.g. "resource struct cleanup" or "integer overflow". |
mort_examples | List or read the compiler's example programs. |
mort_version | Compiler 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
pip install ".[test]" "ruff==0.16.0" "mypy==2.3.0" ziglangruff check src tests && mypy --strict src MORT_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