Continue.dev integration
QuarterCharts MCP for Continue.dev.
Wire up QuarterCharts in 30 seconds by adding one block to Continue's config.yaml (or config.json). Continue's agent can then call 11 grounded financial-data tools backed by SEC EDGAR XBRL filings, each value carrying citation provenance back to the source filing. Works in VS Code and JetBrains.
30-second setup
Open the Continue config
Continue.dev reads MCP servers from one of:
~/.continue/config.yaml(default in Continue 0.9+) or~/.continue/config.json(legacy / opt-in). On Windows the path is%USERPROFILE%/.continue/config.{yaml,json}. Open the file your build uses; create it if it doesn't exist.Add the QuarterCharts entry
Use whichever shape matches your config file (YAML or JSON). Both encode the same MCP server descriptor. Continue automatically discovers all 11 tools from
tools/liston connect — no per-tool registration needed.Reload Continue
Use VS Code's "Continue: Reload Config" command (Cmd+Shift+P → Continue: Reload Config) or restart your editor. JetBrains is similar — find "Reload Continue config" in the action menu. The MCP indicator in the Continue sidebar should list quartercharts with 11 tools available.
Test it
In Continue's chat, ask: "Pull AAPL's latest income statement from QuarterCharts." Continue invokes
qc.get_chartand returns the series with citation provenance pointing at the source SEC filing for every value.
YAML config (Continue 0.9+, recommended)
Add this block to your existing ~/.continue/config.yaml under the top-level mcpServers key (create the key if it doesn't exist yet):
mcpServers:
- name: quartercharts
type: streamable-http
url: https://api.quartercharts.com/mcpContinue's YAML MCP shape uses a list (mcpServers: with - name: entries) — different from Cursor's nested-object shape. The type field is required in YAML.
JSON config (legacy / opt-in)
Older Continue installs (or users who explicitly opted into JSON) use ~/.continue/config.json. Add the experimental.modelContextProtocolServers block:
{
"experimental": {
"modelContextProtocolServers": [
{
"name": "quartercharts",
"transport": {
"type": "streamable-http",
"url": "https://api.quartercharts.com/mcp"
}
}
]
}
}On Continue 0.10+ the JSON shape moved out of experimental to top-level mcpServers (mirroring the YAML form). If the snippet above doesn't load, drop the experimental wrapper and place modelContextProtocolServers (or its rename to mcpServers) at the root.
SSE transport (compatibility shim)
Continue 0.8 and earlier shipped without Streamable HTTP support. If your build requires SSE, change the type to sse — the same URL works for both transports:
mcpServers:
- name: quartercharts
type: sse
url: https://api.quartercharts.com/mcpStreamable HTTP is recommended (lower latency, no long-poll connection overhead). Use SSE only if your build explicitly errors on the HTTP transport.
With an API key (higher limits + Pro-only tools)
Mint a free key at /dashboard/api-keys and add it as an Authorization header. Free keys raise rate limits beyond anonymous; Pro keys also unlock the Pro-only tools (pension disclosures, debt schedule, share-count history with split adjustment).
mcpServers:
- name: quartercharts
type: streamable-http
url: https://api.quartercharts.com/mcp
requestOptions:
headers:
Authorization: Bearer qc_live_your_key_hereContinue forwards requestOptions.headers verbatim on every MCP request. For the JSON form, nest headers inside the transport object instead. Treat the key like any other secret — don't commit it to a public repo.
What Continue can call
All 11 tools currently shipped on the live MCP surface. Full input schemas at /mcp/tools.
| Tool | What it does |
|---|---|
| qc.get_chart | Full chart series (income / cashflow / balance / key-metrics). |
| qc.get_metric | Single named metric series (ROIC, P/E, dividend yield, etc.). |
| qc.get_explanation | Tier-gated metric explanations (free / pro / premium / quant). |
| qc.compare_tickers | Side-by-side comparison of one metric across up to 10 tickers. |
| qc.search_tickers | Substring search over the SEC EDGAR ticker directory. |
| qc.list_metrics | All metric_keys with legal-reviewed tier_content. |
| qc.list_tickers | Accessible ticker universe for the caller's plan. |
| qc.get_segments | Per-segment revenue + margin from XBRL dimensional facts (product/geography). |
| qc.get_pension_disclosuresPro | Funded status + discount rate + service/interest costs per plan type (DB/OPEB). |
| qc.get_debt_schedulePro | Long-term debt schedule per instrument + aggregated maturity wall. |
| qc.get_share_count_historyPro | Split-adjusted diluted-shares-outstanding history per fiscal year. |
Troubleshooting
- Continue doesn't show the quartercharts server in the MCP panel.
- Run "Continue: Reload Config" from the command palette and check the Continue output channel in VS Code for parse errors. Indentation matters in YAML — the entry must be a sibling under
mcpServers:. If the file is JSON, ensure brackets and commas are valid (a missing comma silently disables the whole block). - Tool calls return 429 Too Many Requests.
- You've hit the anonymous-tier rate limit (60 req/min). Mint a free key at /dashboard/api-keys and add the
requestOptions.headersblock from the "With an API key" section above. Free keys raise the limit to 300 req/min. - A Pro-only tool returns 403 Forbidden.
- The pension / debt / share-count tools need a Pro-tier key. Free keys get the 8 core tools. Upgrade at /pricing — Stripe checkout coming Q2 2026; until then email info@quartercharts.com.
- Continue keeps re-connecting / dropping the server.
- If you're on a Continue build older than 0.9 and SSE keepalives time out behind a corporate proxy, switch to Streamable HTTP (the recommended transport). If you can't upgrade, contact info@quartercharts.com with the proxy details and we'll help.
Other clients
QuarterCharts MCP works with any client that speaks JSON-RPC 2.0 over HTTPS. Setup guides for other common clients:
- Cursor & Cline — nested
mcpServersobject in~/.cursor/mcp.json. - Claude Desktop — Anthropic's desktop app; same shape as Cursor but a different config path.
- Raw JSON-RPC — call
POST /mcpdirectly from any HTTP client.