Faim MCP Server

MCP server for FAIM forecasting SDK - Enables Claude to perform time series forecasting using Chronos2 and TiRex models. The faim mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server that integrates the FAIM time series forecasting SDK with any MCP-compatible AI assistant, enabling AI-powered forecasting capabilities.

This MCP server currently exposes two foundation time-series models from the FAIM API for zero-shot forecasting: - Chronos2 - TiRex

• list_models: Returns available forecasting models and capabilities
• forecast: Performs point and probabilistic time series forecasting
• 1D arrays: Single univariate time series
• 3D arrays: batch/sequence/feature format
• Point forecasts (single value predictions)
• Quantile forecasts (confidence intervals)

Its toolset

Everything the assistant can do here goes through one of these:

• Prerequisites — The Prerequisites tool exposed by this server
• Debugging — Enable verbose logging: bash NODE_ENV=development node dist/index.js

Configuration

You will need one environment variable: FAIM_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 20+ - npm 10+ - FAIM API key: Register at https://faim.it.com/ to get your FAIM_API_KEY

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Faim MCP's toolset — Prerequisites, Debugging — is a fair guide to whether it matches your workflow. It is maintained by s-fm; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the faim mcp mcp server does with a few real requests.