MiniZinc MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_solversB | List MiniZinc solvers |
| validate_modelC | Validate a MiniZinc model |
| solve_modelC | Solve a MiniZinc model |
| solve_model_by_pathB | Solve a MiniZinc model given by file paths |
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 4 tools
list_solvers and validate_model are clearly distinct, but solve_model and solve_model_by_path overlap heavily in purpose. The descriptions distinguish file-based solving from a generic solve action, but an agent may be uncertain which to use for an inline model versus a file path.
All tools follow a consistent verb_noun pattern: list_solvers, validate_model, solve_model, solve_model_by_path. The by_path suffix is a clear modifier rather than a convention break.
Four tools is a reasonable scope for a specialized MiniZinc server. Each tool addresses a core workflow need, though the set is slightly minimal.
The server covers the main MiniZinc operations: enumerate solvers, validate a model, and solve a model. Minor gaps exist such as solver-specific configuration or more granular result controls, but the core workflow is not blocked.