NIX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: DEBUG, INFO, WARNING, ERROR | INFO |
| CLEOS_PATH | No | Path to cleos binary if not in PATH (optional) | |
| NODEOS_API | No | Nodeos API endpoint for ABI fetching | http://127.0.0.1:8888 |
| NIX_CONTRACT | No | NIX main contract account | nix |
| RODEOS_ENDPOINT | No | Rodeos HTTP endpoint URL | http://127.0.0.1:8880 |
| NIX_QUERY_CONTRACT | No | NIX query contract account | nix.q |
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
| Name | Description |
|---|---|
| list_queriesB | List all available NIX query actions from the contract ABI |
| get_query_abiB | Get ABI structure and JSON template for a specific query |
| queryC | Execute a NIX query with JSON parameters |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_query_abi retrieves ABI structure, list_queries enumerates available queries, and query executes a query. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern (get_query_abi, list_queries, query) with clear and predictable naming. The verb styles are uniform and readable throughout the set.
With 3 tools, the count is appropriate for the server's purpose of interacting with NIX queries, covering essential operations. It is slightly lean but reasonable, as it includes listing, describing, and executing queries without unnecessary bloat.
The tool set provides core CRUD-like coverage for query operations: list_queries for discovery, get_query_abi for details, and query for execution. A minor gap exists in lacking update or delete operations, but these may not be needed for read-only query workflows.