get_chart_contextLABSCO SUMMARY
Your chart, as the agent sees it, and nothing it can trade with.
It closes the gap where you describe a chart in words and the model guesses: the symbol, the timeframe, the actual bars, your trend lines and your indicator settings all cross over as data. Read-only is enforced rather than promised, since there is no order entry in the tool set, and credentials and account IDs are stripped before context leaves the app.
What it is
A read-only Node server that runs beside the MyLinedChart desktop app and hands an agent the current chart's context: symbol and timeframe, recent OHLCV bars, your drawings, your indicator settings, and the data provider's state.
What you get
- The chart and workspace summary: symbol, timeframe, range, provider, connection state, feed type, counts, diagnostics ID and data freshness
- The most recent OHLCV bars, with epoch-millisecond timestamps
- Every drawing on the symbol — trend lines, horizontal levels, note labels and other overlays
- The configured indicators with their parameters, placement and visibility (settings, not series data)
- IBKR connector and market-data provider status, including whether the feed is delayed or live
- Read-only throughout: no mutations, no order entry, no trading
- Account IDs, credentials, bridge URLs and session tokens stripped before any context is returned
Requirements
Node 18 or later, npm install -g @mylinedchart/mcp-chart-context, and the MyLinedChart desktop app running with MCP enabled under Settings → MCP. It reads a local context file, whose path you can override in configuration, so it only works on the machine the app is on.
Setup effort
One command — npm install -g @mylinedchart/mcp-chart-context
USE CASES
Getting a second opinion on the setup in front of you
The agent reads the symbol, timeframe and recent bars instead of you retyping them.
Discussing the levels you have drawn
Your trend lines, horizontal levels and note labels arrive as data, so the conversation is about the same lines you are looking at.
Checking indicator settings before trusting a signal
Read each indicator's name, calculation parameters and placement — the configuration, not the series.
Working out whether the data is even live
Read the provider status: connection state, feed type, and when it last updated.
Making sure the agent is on the right chart
The context summary reports symbol, range, provider and data freshness in one call.
5 tools
Listed in project docs. Your client may show a different list.
get_candlesget_drawingsget_indicatorsget_provider_statusBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- mlc-mcp on PATH
- Node 18 or later
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npm install -g @mylinedchart/mcp-chart-contextMCP Clients
Claude Desktop, Claude Code
{
"mcpServers": {
"mylinedchart": {
"command": "mlc-mcp"
}
}
}