mcpField
D
Demand Forecasting

Demand Forecasting

Remote
saifs.aiBusiness & Marketing1Updated 6d ago

About Demand Forecasting

A remote MCP server that forecasts product demand from sales history, with optional region or channel breakdowns. It selects models using backtests and can return a script for local processing of larger files.

Key features

  1. 01Daily, weekly, or monthly forecasts
  2. 02Optional region and channel breakdowns
  3. 03Prediction ranges for each forecast
  4. 04Backtest-based model selection
  5. 05Local forecasting script for large files

Use cases

  1. 01Plan orders using lead-time demand
  2. 02Forecast slow or intermittent movers
  3. 03Review expected demand with uncertainty ranges

MCP support

Exposes demand forecasting tools through a remote Streamable HTTP MCP server, with OAuth 2.1 sign-in. For larger files, it can return a Python script that forecasts locally.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://demand-forecaster-mcp.saifs.ai/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Demand Forecasting

Forecasts demand per product (and optionally per region or channel) from sales history — daily, weekly or monthly — with a range for every number. It picks the best-fitting model by backtest, handles slow and intermittent movers (Croston/SBA), refuses to guess when history is too short, and hands lead-time demand to the Inventory Intelligence & Optimizer server for safety stock. Reads Excel, Tally and CSV exports with their own column names.

Registry nameai.saifs/demand-forecasting
Endpointhttps://demand-forecaster-mcp.saifs.ai/mcp
TransportStreamable HTTP (remote, nothing to install)
AuthOAuth 2.1 — PKCE (S256) and dynamic client registration; your client opens a sign-in page on first use
PublisherSAIFS AI

Install

VS Code / GitHub Copilot

Add to .vscode/mcp.json (workspace) or your user mcp.json:

{
  "servers": {
    "saifs-demand-forecasting": {
      "type": "http",
      "url": "https://demand-forecaster-mcp.saifs.ai/mcp"
    }
  }
}

Then start the server from the MCP view and sign in when prompted.

Claude (claude.ai, Desktop)

Settings → Connectors → Add custom connector, and paste:

https://demand-forecaster-mcp.saifs.ai/mcp
Claude Code
claude mcp add --transport http saifs-demand-forecasting https://demand-forecaster-mcp.saifs.ai/mcp
Any other MCP client

Point it at https://demand-forecaster-mcp.saifs.ai/mcp using the Streamable HTTP transport. The server returns 401 with a WWW-Authenticate: Bearer … resource_metadata=… challenge, so OAuth-aware clients sign in automatically.

Tools

ToolWhat it does
demand_forecasterForecasts demand from sales rows (date + quantity is enough; SKU, region, channel and lead time optional) for up to about 200 products and 2,500 rows. Returns forecasts with prediction intervals, the chosen model and its backtest score, and lead-time demand for reordering.
demand_forecaster_get_engineFor larger sales files: returns a runnable Python script that produces the same forecasts locally, so the data never leaves the user's machine.

Example prompts

  • “Here's our Tally sales export. How much of each item will we sell over the next 13 weeks?”
  • “Which products are slow movers, and what should we expect from them next month?”
  • “Forecast monthly demand for spare part SP-220 with a 95% range.”

Support

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.