GitHub Configuration

Created By
dmitryanchikova year ago
Mathematical Optimization MCP Server with PuLP and OR-Tools support
Overview

what is MCP Optimizer?

MCP Optimizer is a mathematical optimization server that supports various optimization problem types using PuLP and OR-Tools.

how to use MCP Optimizer?

To use MCP Optimizer, integrate it with LLM clients like Claude Desktop or Cursor, or run it via Docker or pip installation. Configuration involves adding the server details to the client settings.

key features of MCP Optimizer?

  • Supports multiple optimization problem types including linear programming, assignment problems, and financial optimization.
  • Provides integration with various LLM clients and Docker support.
  • Offers comprehensive testing and production-ready architecture.

use cases of MCP Optimizer?

  1. Solving linear programming problems for resource allocation.
  2. Assigning tasks to workers optimally.
  3. Portfolio optimization for investment management.

FAQ from MCP Optimizer?

  • What types of optimization problems can MCP Optimizer solve?

MCP Optimizer can solve linear programming, assignment, transportation, knapsack, routing, scheduling, and financial optimization problems.

  • Is MCP Optimizer easy to integrate with existing systems?

Yes! It provides various integration methods including Docker, pip, and direct LLM client support.

  • How can I test MCP Optimizer?

You can run comprehensive tests included in the repository to ensure functionality.

Server Config

{
  "mcpServers": {
    "mcp-optimizer": {
      "command": "uvx",
      "args": [
        "mcp-optimizer"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dmitryanchikov
Star
0
Language
Python
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