Ephemeris MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EPHEMERIS_API_KEY | Yes | Your Ephemeris API key (pc_live_...), created in the dashboard at ephemeris.cascade.industries. Used by the local stdio server; remote/HTTP clients instead pass it as an 'Authorization: Bearer pc_live_...' header. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forecastA | Forecast, predict or project one or more numeric time series (sales, demand, traffic, load, prices, metrics, sensor data) with prediction intervals, using Ephemeris' panel of zero-shot foundation models. Mode ensemble is the most accurate: it is level with the top of the TIME benchmark and scores better on GIFT-Eval than any single model in the panel. Returns structured JSON: |
| list_modelsA | Discover the model panel: each model's availability right now (healthy), capabilities (multivariate, covariates, max_horizon, auto_max_horizon), its weight in an ensemble at each horizon, pinned and actually served weight revision, price per thousand series-slots in millicredits and maximum billable context. Call this before using forecast in explicit mode; the deployed panel can differ from any documentation. |
| get_balanceA | Return the account's spendable credit balance in millicredits, excluding credits reserved by in-progress forecasts. 1000 millicredits equal one credit. |
| get_usageB | Return the account's forecast request log, newest first, with the mode, models used, series count, horizon, credits estimated and settled, HTTP status and latency of each request. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: forecasting, checking balance, viewing usage, and discovering models. No overlap or ambiguity between them.
get_balance, get_usage, and list_models follow a consistent verb_noun pattern, while forecast is a verb-only outlier. Still readable and predictable overall.
Four tools are well-scoped for a forecasting service: one core action plus supporting introspection for credits, usage, and model metadata. Each tool earns its place.
Core forecast lifecycle is covered, but there is no way to retrieve a past forecast by request id or cancel an in-progress forecast, which the balance tool hints can exist. Minor gaps an agent can mostly work around.