Skip to main content
Glama
elias-michaias

Onyx Documentation MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
search_onyx_docsB

Search official Onyx programming language documentation

search_github_examplesC

Search Onyx code examples from GitHub repositories by topic

get_onyx_functionsC

Get Onyx function definitions and examples from GitHub

get_onyx_structsC

Get Onyx struct definitions and examples from GitHub

list_github_reposB

List all discovered GitHub repositories with Onyx code

search_all_sourcesC

Search all crawled content (docs, GitHub, URLs)

run_onyx_codeB

Execute Onyx code and return the output/errors for testing and debugging

run_wasmC

Execute a WebAssembly (WASM) file using "onyx run file.wasm" command

build_onyx_codeC

Build Onyx code file using "onyx build" in a specified directory

onyx_pkg_buildC

Build an Onyx package using "onyx pkg build" in a specified directory

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between search_all_sources, search_github_examples, and search_onyx_docs, which could cause confusion about which to use for specific search needs. The build and run tools are clearly differentiated by their actions and targets.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern with snake_case throughout, such as build_onyx_code and run_onyx_code. However, there is a minor deviation with onyx_pkg_build, which uses a slightly different structure (noun_verb) compared to the others.

Tool Count5/5

With 10 tools, the count is well-scoped for a documentation and development server, covering building, running, searching, and retrieving information without being overwhelming. Each tool appears to serve a specific function in the Onyx ecosystem.

Completeness4/5

The toolset provides good coverage for documentation, code execution, and package management, but there are minor gaps such as no tools for updating or deleting resources, or handling configuration. However, the core workflows for development and documentation search are adequately supported.

Maintenance

ActivityInactive
ResponsivenessNo issues