MCP SERVERRun point or probabilistic time-series forecasts on FAIM's hosted models, choosing between Chronos2 and TiRex per call.
LABSCO SUMMARY
The series travels in the call as the x parameter and the model is chosen by name, so switching from TiRex to Chronos2 is a parameter change rather than a new environment. TiRex is univariate only, which puts anything multivariate on Chronos2. The two tools cover choosing a model and running it; storing or fetching the series is not part of the surface.
A two-tool front end for the FAIM forecasting platform: one call lists the models on offer, the other runs the forecast.
A FAIM platform account and its key, supplied as FAIM_API_KEY.
One command plus a key — npm install -g @faim-group/mcp, then supply credentials
USE CASES
You hold the history and want a projection without setting up a modelling environment. The series goes in the call, the horizon is a parameter, and the model is picked by name.
Point forecasts hide their own uncertainty. Asking for probabilistic output with quantiles returns confidence intervals instead of one value.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
forecastPerform time series forecasting using FAIM platform. Supports both point forecasting (single value) and probabilistic forecasting (confidence intervals). Can handle univariate and multivariate time series data. Currently supported models: Chronos2 (default, recommended for multivariate) and TiRex (fast, univariate only).
list_modelsList all available forecasting models and their capabilities. Returns information about Chronos2, TiRex, and other available models, including supported output types and features.
BEFORE YOU INSTALL
2 tools when we connected. list_models only reports which models are reachable (currently Chronos2 and TiRex); forecast does the work in point, quantile and sample modes.
Of the 3 documented setups, 2 run the server on your machine and 1 connects to a hosted endpoint.
CONTEXT COST
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
npm install -g @faim-group/mcphttps://mcp.faim.it.comAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
{
"mcpServers": {
"faim": {
"command": "npx",
"args": [
"-y",
"@faim-group/mcp"
],
"env": {
"FAIM_API_KEY": "<YOUR_FAIM_API_KEY>"
}
}
}
}<YOUR_FAIM_API_KEY> is the FAIM API key you registered for at https://faim.it.com/.
{
"mcpServers": {
"faim": {
"command": "faim-mcp",
"env": {
"FAIM_API_KEY": "<YOUR_FAIM_API_KEY>"
}
}
}
}After npm install -g @faim-group/mcp the command is faim-mcp. <YOUR_FAIM_API_KEY> is the FAIM API key you registered for at https://faim.it.com/.
MCP servers
YuChenSSR
Whatsonyourmind
bradleylab
matlab