macropulse-mcp
An MCP server for MacroPulse: the daily US macro regime as tools for any MCP client that runs local (stdio) servers. Example configs for Claude Code, Claude Desktop and Cursor below. No code to write.
Ask "what macro regime are we in, and what does it mean?" and the agent answers from the live MacroPulse feed.
MacroPulse assigns one of four regimes (expansion, recovery, tightening, risk-off) to every calendar day, weekends included, with a frozen, versioned model: PCA over 13 daily macro and market features, followed by a Statistical Jump Model (v4). The pipeline runs once a day at 21:00 UTC, after the US close.
Requirements
uv, which provides uvx and fetches a suitable Python for you. Alternatively pipx install macropulse-mcp or pip install macropulse-mcp on Python 3.12 or newer, then use macropulse-mcp as the command instead of uvx macropulse-mcp.
Configure
The API key is optional: the public tools work without one. A free key (no credit card) unlocks regime history; forecast, scorecard and liquidity need the Starter or Pro plan. Get a key at macropulse.live.
Claude Code
claude mcp add --transport stdio macropulse -- uvx macropulse-mcp
# with a key:
claude mcp add --env MACROPULSE_API_KEY=mp_your_key --transport stdio macropulse -- uvx macropulse-mcp
Claude Desktop
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"macropulse": {
"command": "uvx",
"args": ["macropulse-mcp"],
"env": { "MACROPULSE_API_KEY": "mp_your_key" }
}
}
}
Leave out env to use only the public tools. Claude Desktop on macOS does not inherit your shell's PATH; if it reports spawn uvx ENOENT, replace "uvx" with the output of which uvx (macOS/Linux) or where uvx (Windows).
Cursor
Add the same block to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"macropulse": {
"command": "uvx",
"args": ["macropulse-mcp"],
"env": { "MACROPULSE_API_KEY": "mp_your_key" }
}
}
}
Tools
All tools are read-only.
| Tool | Needs | Returns |
|---|---|---|
get_current_regime |
nothing | The latest published regime, risk score, the regime's target equity exposure and MacroPulse's fixed one-line description of that regime (a characterization, not advice) |
get_signed_regime |
nothing | The current regime as MacroPulse's Ed25519-signed payload, returned exactly as served (the tool does not verify the signature) |
get_market_snapshot |
nothing | Regime with confidence and persistence, net Fed liquidity z-score and trend |
explain_regimes |
nothing (offline) | What the four regimes mean, their ids and target exposures, how and when the model runs |
get_regime_history |
key (Free: up to 30 rows) | Daily regime, risk score and regime probabilities, newest first; rows before 2026-07-03 are a hindsight backfill; optional limit, start, end |
get_forecast |
key, Starter or Pro | ARIMA projection of the regime probabilities for 1-10 business days (horizon) |
get_scorecard |
key, Starter or Pro | Five normalized macro signals on a -1 to 1 scale |
get_liquidity |
key, Starter or Pro | Net Fed liquidity time series (limit, 1-500) |
API results come back under data, next to a source field that marks them as third-party data rather than instructions for the agent. When a call fails, the tool returns a one-line error; for a missing or invalid key, a plan that lacks the data, a rate limit or an outage it says what to do next. The key is sent only in the X-MacroPulse-Key header and is never logged or echoed.
The four regimes
| Regime | id | Target equity exposure |
|---|---|---|
| Expansion | 0 | 100% |
| Recovery | 1 | 75% |
| Tightening | 2 | 25% |
| Risk-Off | 3 | 0% |
The exposure is a rule of thumb attached to each label, not a recommendation for any portfolio. Regimes for dates before 2026-07-03, when v4 went live, are a backfill computed with hindsight.
Environment
| Variable | Default | Purpose |
|---|---|---|
MACROPULSE_API_KEY |
unset | API key for the keyed tools |
MACROPULSE_API_BASE |
https://api.macropulse.live |
API URL override for testing (https only; plain http only for localhost) |
MACROPULSE_API_BASE receives your API key. Every keyed call sends MACROPULSE_API_KEY to that host, so point it only at hosts you trust (normally leave it unset). Redirects are never followed.
Development
pip install -e ".[dev]"
pytest # offline: the API is mocked
MACROPULSE_LIVE_SMOKE=1 pytest -m live # optional: read-only, public endpoints, no key
Disclaimer
MacroPulse data is informational only and is not investment advice.
Links
macropulse.live · API docs · IRL, pre-execution compliance for trading agents, which uses the signed MacroPulse regime
License
MIT
Metadata
Release files for macropulse-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| macropulse_mcp-0.2.0.tar.gz | 32.1 kB | With provenance | Details for macropulse_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| macropulse_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for macropulse_mcp-0.2.0-py3-none-any.whl |
Total release size: 48.3 kB
Release files / macropulse_mcp-0.2.0.tar.gz
| Download URL | macropulse_mcp-0.2.0.tar.gz |
|---|---|
| Size | 32.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
347cceccd1043dc26437d95e39b72c58de41b17a2eca799104f7cbb4886c9d67
|
|
BLAKE2b-256 checksum How to use checksums |
2f565d45c941c62fbdd8f7b29c0e6f4d8488857089f8c9396a42c9a0f347859d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logRelease files / macropulse_mcp-0.2.0-py3-none-any.whl
| Download URL | macropulse_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 16.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36209947b32bb5b143d3d32596f843d1113e87ac9c47e15ea124936b7cd756d7
|
|
BLAKE2b-256 checksum How to use checksums |
c6838b742e840759d3a6ef3f9e534dc359a9fc8a49eb7709c972338c7d5ddc0d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for macropulse-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for macropulse_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.