Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Macro events, earnings & market data from QuantGist for Claude and other AI agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
QUANTGIST_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"quantgist": {
"command": "uvx",
"args": [
"quantgist-mcp"
],
"env": {
"QUANTGIST_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add quantgist --env QUANTGIST_API_KEY=your-value -- uvx quantgist-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"quantgist": {
"command": "uvx",
"args": [
"quantgist-mcp"
],
"env": {
"QUANTGIST_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"quantgist": {
"type": "stdio",
"command": "uvx",
"args": [
"quantgist-mcp"
],
"env": {
"QUANTGIST_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account QuantGist-Technologies, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: QUANTGIST_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.4) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Exposes QuantGist macro-economic event data as Model Context Protocol (MCP) tools so Claude and other AI agents can query calendars, check event proximity, and assess trade safety — all within a conversation.
The server registers 22 tools that any MCP-compatible client (Claude Desktop, Claude Code, custom agents) can call:
Macro economic events
| Tool | Description |
|---|---|
get_upcoming_events | Events scheduled in the next N hours, filtered by impact |
get_events_range | Events in a date range with optional country/symbol/impact filters |
get_economic_calendar | Full day macro calendar from /calendar, grouped by time, with coverage/warnings metadata |
get_event_detail | Full details for one event by ID (actual, forecast, previous, symbols) |
Earnings
| Tool | Description |
|---|---|
get_earnings_upcoming | Next upcoming earnings reports across all tickers, with EPS/revenue estimates |
get_earnings_for_ticker | Earnings history for one ticker (estimate vs actual, beat/miss, EDGAR links) |
get_earnings_summary | Beat / miss / in-line counts and overall beat rate for a ticker |
get_earnings_surprises | Largest EPS surprises across the market in the latest reports |
get_earnings_season_summary | Index-level summary of the current earnings season |
Markets
| Tool | Description |
|---|---|
get_markets_overview | End-of-day quotes for major indices and instruments (S&P 500, Nasdaq, gold, oil…) |
Discovery & help (read-only, no API key required)
| Tool | Description |
|---|---|
get_pricing | Plans, prices, and feature gates (free → enterprise) + the Bot Usage Add-On |
get_limits | Per-plan caps: request quotas, history window, data delay, WS, watchlists, rate limiting |
recommend_endpoint | Map a natural-language use case to the best REST endpoint + MCP tool |
get_status | Check API reachability and link the public status page |
estimate_usage_cost | Estimate which plan fits a request volume + overage / Bot Usage Add-On notes |
Account (webhooks, API keys, billing)
| Tool | Description |
|---|---|
get_subscription | Current plan, status, and billing period (read-only) |
list_webhooks | Registered webhook endpoints (read-only; Pro plan) |
create_webhook | Register an HTTPS webhook endpoint — confirm-gated; signing secret shown once |
delete_webhook | Permanently delete a webhook endpoint — confirm-gated, destructive |
test_webhook | Send a signed synthetic test delivery to verify your consumer |
create_api_key | Create a (optionally scoped) API key — confirm-gated; key shown once |
create_checkout_session | Create a Stripe Checkout session for a plan upgrade — confirm-gated; never charges |
Mutating tools follow an explicit human-in-the-loop pattern:
create_checkout_session never charges anything — it returns a Stripe-hosted checkout URL that a human must open in a browser and complete. No card data ever passes through the tool or QuantGist's API. The plan upgrades automatically after payment.The MCP server is hosted over HTTP at `https://api.quantgist.com/mcp` — no install, no Python. Any client that supports the streamable-HTTP transport can connect by sending your QuantGist key in an X-API-Key header (multi-tenant: billed to your own quota).
Claude Code, in one command:
claude mcp add --transport http quantgist https://api.quantgist.com/mcp \
--header "X-API-Key: qg_live_YOUR_KEY"
Any streamable-HTTP MCP client:
{
"mcpServers": { "quantgist": { "type": "streamable-http", "url": "https://api.quantgist.com/mcp", "headers": { "X-API-Key": "qg_live_YOUR_KEY" } } } }
Connectors that only accept a URL (e.g. ChatGPT): if you can't set a custom header, put the key in the URL instead — https://api.quantgist.com/mcp?apiKey=qg_live_YOUR_KEY (also accepts Authorization: Bearer ). The header is preferred where possible, since a key in the URL can be recorded in proxy/server logs.
Prefer to run it yourself? Install locally (below) or self-host the HTTP server — see DEPLOY.md.
pip install quantgist-mcp
uv pip install quantgist-mcp
git clone https://github.com/QuantGist-Technologies/QuantGist_MCP
cd QuantGist_MCP uv sync # installs all dependencies into a venv uv run quantgist-mcp # start the server
Locate your Claude Desktop config file:
| Platform | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Add the quantgist server block (see claude_desktop_config_example.json):
{
"mcpServers": { "quantgist": { "command": "quantgist-mcp", "env": { "QUANTGIST_API_KEY": "qg_live_YOUR_KEY_HERE" } } } }
Restart Claude Desktop after saving. The tools will appear in the tool list.
uv run instead of a global installIf you prefer not to install globally, point Claude Desktop at uv run:
{
"mcpServers": { "quantgist": { "command": "uv", "args": ["run", "--directory", "/absolute/path/to/Quangist_MCP", "quantgist-mcp"], "env": { "QUANTGIST_API_KEY": "qg_live_YOUR_KEY_HERE" } } } }
Add to .claude/mcp_settings.json in your project (or the global ~/.claude/mcp_settings.json):
{
"mcpServers": { "quantgist": { "command": "quantgist-mcp", "env": { "QUANTGIST_API_KEY": "qg_live_YOUR_KEY_HERE" } } } }
Besides the stdio transport above, the server can run as a hosted HTTP service via the quantgist-mcp-http entry point (GET /health, MCP at /mcp). It accepts a per-request X-API-Key header (multi-tenant) or a server-side QUANTGIST_API_KEY env var.
docker build -t quantgist-mcp .
docker run -p 8000:8000 -e QUANTGIST_API_KEY=qg_live_YOUR_KEY quantgist-mcp curl http://localhost:8000/health
See DEPLOY.md for Docker, Docker Compose, and Coolify deployment.
get_upcoming_eventsReturns events in the next N hours.
| Parameter | Type | Default | Description | |||
|---|---|---|---|---|---|---|
hours | integer (1–168) | 24 | Look-ahead window in hours | |||
impact | high \ | medium \ | low \ | all | high | Impact filter |
get_events_rangeReturns events in a date range.
| Parameter | Type | Required | Description | |||
|---|---|---|---|---|---|---|
from_date | ISO string | Yes | Start date/datetime | |||
to_date | ISO string | Yes | End date/datetime | |||
country | string | No | 2-letter country code (e.g. "US") | |||
impact | enum | No | high \ | medium \ | low \ | all |
symbol | string | No | Trading symbol (e.g. "XAUUSD") |
get_economic_calendarReturns the day's macro calendar grouped by release time. This tool calls GET /v1/calendar?envelope=true, not the broad /events feed, so general financial-news headlines are not mixed into scheduled macro releases.
The structured output preserves the backend envelope:
events / count / returned_counttotal_countcoveragewarningstruncatedschema_versionIf the backend response is partial, stale, truncated by the MCP safety cap, or missing the required calendar envelope, the tool surfaces that in warnings and does not fall back to /events.
| Parameter | Type | Default | Description |
|---|---|---|---|
date | ISO date | today (UTC) | Date to fetch |
impact | enum | high | Impact filter |
get_event_detailReturns full detail for one event.
| Parameter | Type | Required | Description |
|---|---|---|---|
event_id | string | Yes | Event ID from any other tool |
get_earnings_upcomingReturns the next upcoming earnings reports across all tickers, ordered by report date.
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer (1–100) | 20 | Number of upcoming reports to return |
get_earnings_for_tickerReturns earnings history for a single ticker (EPS estimate vs actual, revenue, beat/miss, EDGAR links).
| Parameter | Type | Default | Description |
|---|---|---|---|
ticker | string | required | Stock ticker, e.g. "AAPL" |
limit | integer (1–50) | 10 | Number of historical reports to return |
get_earnings_summaryReturns beat / miss / in-line counts and overall beat rate for a ticker.
| Parameter | Type | Required | Description |
|---|---|---|---|
ticker | string | Yes | Stock ticker, e.g. "AAPL" |
get_earnings_surprisesReturns the largest EPS surprises across the market in the most recent reports.
| Parameter | Type | Default | Description |
|---|---|---|---|
limit | integer (1–50) | 20 | Number of top surprises to return |
get_earnings_season_summaryReturns the index-level summary of the current earnings season (total reports, overall beat rate, average EPS surprise, season label). No parameters.
get_markets_overviewReturns end-of-day quotes for major market indices and instruments (S&P 500, Nasdaq, Dow Jones, gold, oil, etc.). No parameters.
get_subscriptionReturns the authenticated account's plan, status, and billing period. No parameters. Read-only.
list_webhooksLists the account's registered webhook endpoints. No parameters. Read-only; webhooks require the Pro plan.
create_webhookRegisters an HTTPS webhook endpoint (Pro plan). Confirm-gated: without confirm: true it returns a preview and makes no API call. The signing secret is returned once only.
| Parameter | Type | Default | Description |
|---|---|---|---|
url | string (required) | — | HTTPS URL that will receive event POSTs |
events | string[] | ["*"] | Event types: economic_release, earnings, earnings.scheduled, earnings.confirmed, earnings.reported, earnings.surprise, news.radar.breaking, or * |
impact_filter | string[] | — | Only deliver events with these impact levels, e.g. ["high"] |
confirm | boolean | false | Must be true to actually create |
delete_webhookPermanently deletes a webhook endpoint and its delivery history. Confirm-gated and destructive.
| Parameter
Only the beginning is shown; read the rest in the repo