Macro Snapshot
macro-snapshot MCP — the state of the economy in one call.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http macro-snapshot 'https://gateway.pipeworx.io/macro-snapshot/mcp'{
"mcpServers": {
"macro-snapshot": {
"type": "http",
"url": "https://gateway.pipeworx.io/macro-snapshot/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
mcp-macro-snapshot
macro-snapshot MCP — the state of the economy in one call.
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
macro_snapshot | Get the current state of the US/global economy in ONE call — Fed funds rate, the full Treasury yield curve (3mo/2y/10y + 10y-2y and 10y-3m spreads with inversion flag), CPI & core CPI year-over-year, unemployment, nonfarm payrolls (+1mo change), real GDP growth, S&P 500, VIX, the broad USD index, and BTC. Composes 16 FRED series (Federal Reserve economic data) with live crypto, runs them in parallel, and returns a structured dashboard plus human-readable callouts (curve inversion, inflation vs the Fed's 2% target, elevated VIX). Use this instead of fetching ten indicators separately. No arguments. THE COMPONENTS DO NOT SHARE A DATE — daily series (rates, markets) sit beside quarterly GDP that can be 100+ days older; each group carries its own as_of map and freshness states the full span and oldest component — read those before comparing fields against the top-level as_of, which is only the newest daily series. |
indicator | Read recent history for a single FRED (Federal Reserve economic data) series — drill into anything in the macro_snapshot or any other FRED series id. Common ids: UNRATE (unemployment), DFF (Fed funds), DGS10/DGS2/DGS3MO (Treasury yields), CPIAUCSL (CPI index), CPILFESL (core CPI index), PAYEMS (nonfarm payrolls), VIXCLS (VIX), SP500, MORTGAGE30US (30y mortgage rate), WALCL (Fed balance sheet), DTWEXBGS (broad USD index), T10Y2Y/T10Y3M (curve spreads). Returns observations most-recent-first plus the latest value. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"macro-snapshot": {
"url": "https://gateway.pipeworx.io/macro-snapshot/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/macro-snapshot/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/macro_snapshot \
-H 'Content-Type: application/json' \
-d '{}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/macro_snapshot. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"macro-snapshot": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-macro-snapshot"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-macro-snapshotIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Macro Snapshot data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Questions fréquentes
Qu'est-ce que Macro Snapshot ?
macro-snapshot MCP — the state of the economy in one call.
Comment installer Macro Snapshot ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http macro-snapshot 'https://gateway.pipeworx.io/macro-snapshot/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Macro Snapshot ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Macro Snapshot est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Macro Snapshot ?
Il est publié par pipeworx-io. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.