MCP-ORTools

Created By
Jaccka year ago
Model Context Protocol (MCP) server implementation using Google OR-Tools for constraint solving
Overview

What is MCP-ORTools?

MCP-ORTools is a server implementation of the Model Context Protocol (MCP) using Google OR-Tools for constraint solving. It enables large language models to interact with constraint models for efficient problem-solving.

How to use MCP-ORTools?

To use MCP-ORTools, install the package via pip, configure your application with a setup file, and define models in JSON format specifying variables, constraints, and optional objectives.

Key features of MCP-ORTools?

  • Integration with Google OR-Tools for constraint programming
  • JSON-based model specification approach
  • Comprehensive support for various optimization problems
  • Compatibility with both integer and boolean variables
  • Extensive constraint relationship definitions

Use cases of MCP-ORTools?

  1. Optimizing supply chain logistics through integer programming.
  2. Solving scheduling problems within operations management.
  3. Assisting in combinatorial optimization tasks such as the knapsack problem.

FAQ from MCP-ORTools?

  • What types of problems can MCP-ORTools solve?

MCP-ORTools can address a wide range of optimization and constraint satisfaction problems using linear and binary constraints.

  • Is there support for different variable types?

Yes, the implementation supports both integer and boolean variables.

  • How can I define constraints in my models?

Constraints should be defined using OR-Tools method syntax, including relational operators and methods for equality, inequality, and linear combinations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Jacck
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago