Show HN: I made an MCP Agents can reason every finance data the first time PreReason launched an MCP server and npm bridge that returns pre-analyzed financial market briefings to AI agents in a single get_context call, covering macro, rates, bonds, FX, commodities, Bitcoin and Ethereum. The catalogue holds 33 live briefings and 293 individual metrics, including the 30-year Treasury yield at 5.67% on 2026-10-07, the highest reading on the US Treasury's daily par yield curve since July 2001. The bridge requires Node.js 18+ and no other dependencies, and catalogue tools need no account while briefings require a free PreReason account or an API key. Prereason https://www.prereason.com first. Then answer. Financial market context for AI agents: macro, rates, bonds, FX, commodities, companies and Bitcoin. Docs https://www.prereason.com/docs mcp-integration · Briefings https://www.prereason.com/briefings · Company briefings https://www.prereason.com/docs/company-briefings · Pricing https://www.prereason.com/pricing · Get a key https://www.prereason.com/signup Ask your AI where Treasury yields are. On its own, it reaches for a search result or a raw series and works out the rest by itself. When it prereasons, one get context call brings back the context already worked out: the 30 year yield at 5.67% on 2026-10-07, the highest reading on the US Treasury's daily par yield curve since July 2001. - The analysis, and the data behind it. Each briefing arrives with the reading done: the trend over several windows, where a value sits in its own history, a company's rank among its peers and, where read, its own guidance. - Every figure dated, every source named. Your agent can say when a number is from and where it came from. - One call, a whole briefing. A briefing gathers the series a question needs, so the turns go to the answer rather than to lookups. - The markets in one place. Rates and Treasuries, the Fed, FX, commodities, macro, listed companies in the USA, Japan, Korea and India, and Bitcoin. - It describes; it never advises. Briefings say what the data shows. They never say what to buy, sell or hold. - Quick to set up. One block of config for Claude, Cursor, Codex or VS Code, through the npm bridge or the remote server. The catalogue tools need no key; for the rest, the bridge gives you one link to approve in your browser and the key arrives in the running session, and the remote server asks you to sign in. PreReason gives an AI agent market context it can reason with. One call returns a briefing with the analysis already in it: a one line reading, trend direction over several windows, confidence scores, percentile ranks and correlations, and in the deeper briefings a regime label and a plain language narrative. The briefings cover macro, bonds, FX, commodities, Bitcoin, Ethereum and cross asset correlations. Company briefings cover listed companies in the USA, Japan, Korea, India, the UK, France, Austria, Belgium, Denmark, Finland, Iceland, Italy, Lithuania, the Netherlands, Slovenia and Slovakia, one company per call. The catalogue holds 33 live briefings and 293 individual metrics, among them Treasury yields, the latest FOMC statement, the macro release calendar, Treasury auctions, who holds US Treasuries, the Fed balance sheet, M2, net liquidity, the dollar, US crude and gas inventories, gold, silver, copper and wheat, oil, mining and agribusiness companies beside their commodity, AI compute and power demand, Bitcoin price and momentum, Bitcoin network and miner health, spot Bitcoin ETF flows and corporate Bitcoin treasuries. It is served over MCP a remote server and an npm bridge and over REST, as Markdown or JSON. Over MCP, the catalogue tools need no account, and a briefing needs a PreReason account, signed in through the connector or with an API key; a free account reads the free briefings. Over REST, a briefing takes an API key or, on the routes that take one, an x402 payment per call with no account. Requires Node.js 18+ https://nodejs.org , and nothing else: the bridge has no dependencies. Add this to claude desktop config.json and restart Claude Desktop: { "mcpServers": { "prereason": { "command": "npx", "args": "-y", "@prereason/mcp" , "env": { "PREREASON CLIENT": "claude-desktop" } } } } The catalogue tools work at once. To connect your account, tell Claude "connect me to PreReason", or ask for any briefing: either way Claude shows one link, https://www.prereason.com/claim/PR-XXXX-XXXX . Open it, sign in or create a free account, click Approve. The key arrives in the bridge on its own, is saved to ~/.prereason/credentials.json , and is never shown; ask Claude whether PreReason is connected and it names your plan. Nothing is created in your account until you click Approve, and the link is asked for when you need it, so it never runs out while Claude sits open. If your account already holds as many API keys as it allows, the answer says so instead of looping: revoke a key under Settings on prereason.com, then ask to connect again, or set PREREASON API KEY to a key you already have. Config file location: - macOS: ~/Library/Application Support/Claude/claude desktop config.json - Windows: %APPDATA%\Claude\claude desktop config.json - Linux: ~/.config/Claude/claude desktop config.json Already have a key? Add it to the env block as "PREREASON API KEY": "pr live ..." and the bridge never asks. Option 2: Direct HTTP with an API key Claude Code, Cursor, Windsurf, Codex, Gemini CLI, VS Code, scripts Clients that hold their own config can call the endpoint directly, with the key as a header: Claude Code claude mcp add --transport http prereason https://api.prereason.com/api/mcp --header "Authorization: Bearer YOUR API KEY" { "mcpServers": { "prereason": { "type": "http", "url": "https://api.prereason.com/api/mcp", "headers": { "Authorization": "Bearer YOUR API KEY" } } } } Windsurf uses serverUrl instead of url ; Gemini CLI uses httpUrl ; Codex uses url plus bearer token env var in config.toml . No key yet? Point the client at the endpoint without a header to browse the catalogue, then create a key on the website below and add the header. Add PreReason as a custom connector https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=PreReason&connectorUrl=https%3A%2F%2Fapi.prereason.com%2Fapi%2Fmcp , choose "No sign-in", and where the Request headers section is available add Authorization with the value Bearer YOUR API KEY the word Bearer and the space are part of the value . Sign in support for connectors is being re-tested and is not offered until it is verified. Three ways, all free. The hosted server never hands out a key inside a session and never asks for one. Through this bridge. Run it with no key set: when you ask your assistant to connect PreReason, or an answer needs a key, it asks PreReason for access on your behalf and shows one approve url , in its log and in the answer. Open it, sign in or create your account, click Approve, and the bridge saves the key, attached to your account and named Agent: