Skip to main content
Glama
PreReason

PreReason-mcp

@prereason/mcp

npm version License: MIT PreReason/mcp MCP server

MCP server for PreReason — the Context API for financial agents.

PreReason returns pre-reasoned market briefings: trend signals, regime classification, confidence scores, cross-asset correlations, and causal narratives. Use it when your agent needs to reason about market conditions, not parse raw price feeds.

Quick Start

Option 1: Direct HTTP (Claude Code, Cursor, Windsurf, etc.)

Clients that support remote MCP servers can connect directly with no bridge package needed.

# Claude Code (CLI one-liner)
claude mcp add prereason --transport http https://api.prereason.com/api/mcp

Or add to .mcp.json / your client's MCP config:

{
  "mcpServers": {
    "prereason": {
      "type": "http",
      "url": "https://api.prereason.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Option 2: stdio bridge (Claude Desktop and other stdio-only clients)

Requires

Add to your MCP client config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "prereason": {
      "command": "npx",
      "args": ["-y", "@prereason/mcp"],
      "env": {
        "PREREASON_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Claude Desktop config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Restart your MCP client after editing the config. PreReason should appear with 5 tools.

Get an API Key

  1. Sign up at prereason.com/signup

  2. Go to Dashboard > Settings > API Keys

  3. Copy your key (starts with pr_live_)

5 MCP Tools

Tool

Auth

Description

list_briefings

Open

List all 17 pre-reasoned market briefings with tier requirements

list_metrics

Open

List all 38 available metrics: 30 API + 8 mining/energy (filterable by category)

get_health

Open

API health check, version, account tier

get_context

Required

Fetch a pre-reasoned market briefing (markdown or JSON)

get_metric

Required

Fetch a single metric with trend/signal/percentile

17 Market Briefings

Free (6 briefings)

Briefing

Description

btc.quick-check

Minimal fast context: BTC + Net Liquidity + correlation

btc.context

BTC + liquidity + hash ribbon + difficulty + momentum

macro.snapshot

Fed balance, M2, treasury yields, VIX, net liquidity

cross.correlations

BTC correlation matrix vs macro indicators

btc.pulse

Volume, fees, mempool analysis

btc.grid-stress

Epoch pace and difficulty adjustment forecast

Basic - $19.99/mo (5 briefings)

Briefing

Description

btc.momentum

200D MA support/resistance with 7d/30d/90d momentum and YTD percentiles

macro.liquidity

Liquidity indicators with momentum analysis

btc.on-chain

Hash rate, difficulty, fees, mempool health

cross.breadth

Cross-asset breadth with SPY, DXY, VIX

btc.miner-survival

Hashprice thermometer with miner stress scoring

Pro - $49.99/mo (6 briefings)

Briefing

Description

btc.full

Complete market intelligence with all metrics and analysis

btc.factors

Multi-factor attribution for BTC price movements

cross.regime

Regime classification (risk-on/risk-off/transition) with USDT.D risk sentiment

fx.liquidity

FX environment with DXY, treasury, and global liquidity

btc.energy

Production cost model with gas input pressure

btc.treasury

Corporate Bitcoin treasury intelligence from SEC filings

Example Prompts

Once connected, try prompts like:

  • "What's the current BTC regime?"

  • "Show me the macro snapshot"

  • "What does the full context briefing say about market conditions?"

  • "Get the bitcoin price metric with trend analysis"

  • "What's the hash ribbon signal right now?"

  • "List available briefings"

Troubleshooting

"Server disconnected" error

  • Ensure Node.js 18+ is installed: node --version

  • Check your API key starts with pr_live_

  • Fully quit Claude Desktop (system tray > Quit) and reopen

Tools not appearing

  • Restart Claude Desktop after editing config

  • Verify JSON syntax: node -e "JSON.parse(require('fs').readFileSync('path/to/config','utf8'))"

Windows: "'C:\Program' is not recognized"

If you still see this error, ensure you're using the env block (not --header args) as shown in Quick Start above. If the issue persists, install globally and use node:

  1. Run: npm install -g @prereason/mcp

  2. Use this config (replace YOUR_USER with your Windows username):

{
  "mcpServers": {
    "prereason": {
      "command": "node",
      "args": [
        "C:\\Users\\YOUR_USER\\AppData\\Roaming\\npm\\node_modules\\@prereason\\mcp\\bin\\cli.js"
      ],
      "env": {
        "PREREASON_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Auth errors on get_context / get_metric

  • list_briefings, list_metrics, and get_health work without a key

  • get_context and get_metric require a valid API key

  • Get a free key at prereason.com/signup

Other MCP Clients

If your client supports remote HTTP servers, use Quick Start Option 1 above. The stdio bridge package is only needed for clients that require stdio transport (e.g. Claude Desktop).

CLI Usage

# Using environment variable (recommended)
PREREASON_API_KEY=pr_live_... npx @prereason/mcp

# Using --header flag (backward compatible)
npx @prereason/mcp --header "Authorization:Bearer YOUR_API_KEY"

# Custom URL
PREREASON_URL=https://custom.endpoint/mcp npx @prereason/mcp

# Help
npx @prereason/mcp --help

License

MIT

Install Server
A
security – no known vulnerabilities
A
license - permissive license
A
quality - confirmed to work

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PreReason/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server