Voidlang MCP Server

LLMs are terrible at writing valid syntax in a brand-new language, but they are excellent at outputting JSON arrays. VoidLang flips the contract: the

Local serverstdioGo

What is the Voidlang MCP server?

Connect Voidlang to Claude, Cursor or any other MCP client and it stops being a tab you switch to. LLMs are terrible at writing valid syntax in a brand-new language, but they are excellent at outputting JSON arrays. VoidLang flips the contract: the language is a JSON array of [opcode, args…] pairs. The compiler does all of the work. The voidlang mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • One — shot ISA endpoint returns the entire instruction set in one call — no per-call schema discovery
  • Production-grade — stdlib-only server, multi-stage Dockerfile, healthcheck, Railway-ready
  • Method — Path
  • GET — /
  • POST — /compile
  • Var — Default
  • PORT — 7070
  • VOIDMCP_ALLOW_RUN — unset
  • VOIDMCP_PUBLIC_BASE — autodetected
  • Examples — The Examples tool exposed by this server

Installation

Installation goes through your MCP client rather than a global install: point it at @railway/cli on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Voidlang's toolset — One, Production-grade, Method and 7 more — is a fair guide to whether it matches your workflow. It is maintained by 24greyhat; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Voidlang's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Voidlang.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Oneshot ISA endpoint returns the **entire** instruction set in one call — no per-call schema discovery.
Production-gradestdlib-only server, multi-stage Dockerfile, healthcheck, Railway-ready.
MethodPath
GET/
POST/compile
VarDefault
PORT7070
VOIDMCP_ALLOW_RUNunset
VOIDMCP_PUBLIC_BASEautodetected
ExamplesThe Examples tool exposed by this server.

How to install the Voidlang MCP server

{
  "mcpServers": {
    "voidlang": {
      "command": "/absolute/path/to/build/voidmcp",
      "args": ["stdio"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Voidlang to One.
  • Use Voidlang to Production-grade.
  • Use Voidlang to Method.

Frequently asked questions

It connects Voidlang to MCP-compatible AI assistants such as Claude and Cursor, exposing 10 tools (One, Production-grade, Method, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Voidlang directly.