search_onyx_docsLABSCO SUMMARY
Search plus a compiler, so the answer can be checked before you get it.
Documentation search for a small language is only half useful — the examples run out. Here the build and run tools close the loop: code is written, compiled, and the compiler's errors come straight back, so what you are handed has been through the compiler rather than around it. Crawling is not exposed as a tool, so nothing in a conversation can trigger a re-index.
What it is
A server for the Onyx programming language. It searches the official documentation and indexed GitHub repositories for examples, function definitions and struct definitions, and it compiles and runs Onyx code so compiler errors come back as output rather than guesses.
What you get
- Official documentation searched
- GitHub code examples searched by topic, plus function and struct definitions pulled from those repositories
- The list of repositories that have been indexed
- One search across every source at once
- Onyx code executed in a sandbox and its output or errors returned
- Code built in a project directory you name, and a package built the same way
- WebAssembly executed and its output returned
- A read-only interface — crawling is a command-line operation and is deliberately not exposed as a tool
Requirements
The Onyx compiler installed and on the path for anything that builds or runs code, and Node for the server. The README also points to a hosted instance at mcp.onyxlang.io, but that address did not resolve in September 2026, so run it from a local clone and populate the index yourself from the command line.
Setup effort
Build from source — git clone https://github.com/elias-michaias/onyx_mcp.git
USE CASES
01
Finding out how something is done in Onyx
Search the documentation, or search every source at once when you do not know whether the answer is in the docs or in code.
02
Looking for real code rather than a documentation snippet
Search the indexed repositories by topic and see which ones were indexed at all.
03
Checking a function or struct signature
Pull the definition from the repositories instead of inferring it from usage.
04
Making sure the code compiles before you use it
Run it in the sandbox and let the compiler's errors drive the next revision.
05
Building into your own project directory
Build the file or the whole package where you actually work, so the output is something you can run.
10 tools
Listed in project docs. Your client may show a different list.
search_github_examplesget_onyx_functionsget_onyx_structslist_github_repossearch_all_sourcesrun_onyx_coderun_wasmbuild_onyx_codeonyx_pkg_buildBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- node and npm on PATH
- The Onyx compiler installed and on PATH (for the build and run tools)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/elias-michaias/onyx_mcp.git
cd onyx_mcp
npm install
cp .env.example .envOptionally edit .env and add a GitHub token (GITHUB_TOKEN) for higher rate limits.
Populate the search index — crawling runs only from the command line, not through the MCP tools:
TERMINAL
npm run crawl:allThen point the client at src/index.js in this folder:
MCP Clients
Claude Desktop — local
CLAUDE DESKTOP — LOCAL · JSON
{
"mcpServers": {
"onyx": {
"command": "node",
"args": [
"<YOUR_PATH_TO_ONYX_MCP>/src/index.js",
"server"
]
}
}
}
