Skip to main content
Glama
carban

MiniZinc MCP Server

by carban
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MiniZinc MCP Server

No user-submitted related servers found.

    Related Servers

    • minizinc-mcp

      r33drichards
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables solving constraint satisfaction and optimization problems using MiniZinc models via a single tool.
      4
      MIT

    • mcp-solver

      szeider
      A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server that exposes MiniZinc constraint solving capabilities to Large Language Models.
      184
      MIT

    • MCP Solver

      swesmith-repos
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that enables Large Language Models to interactively create, edit, and solve constraint models using backends like MiniZinc, Z3, PySAT, and Clingo. It bridges natural language with symbolic reasoning for solving complex logical, SAT, SMT, and optimization problems.
      MIT

    • CHUK MCP Solver

      IBM
      A
      license
      A
      quality
      D
      maintenance
      Provides constraint satisfaction and optimization capabilities to LLMs and AI agents for scheduling, resource allocation, routing, budget optimization, and configuration problems using Google OR-Tools CP-SAT solver.
      5
      5
      Apache 2.0

    • Google OR-Tools server

      Jacck
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP-ORTools integrates Google's OR-Tools constraint programming solver with Large Language Models through the MCP, enabling AI models to: Submit and validate constraint models Set model parameters Solve constraint satisfaction and optimization problems Retrieve and analyze solution
      21
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    Four tools is a reasonable scope for a specialized MiniZinc server. Each tool addresses a core workflow need, though the set is slightly minimal.

    Completeness4/5

    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.

    Resources