A Model Context Protocol server that gives AI assistants like Claude expert-level help with the ApexCharts ecosystem: charts, gantt, tree, sankey, grid, stock, and maps. It generates valid configs, catches common mistakes, and serves the official knowledge base for each product on demand, so the AI gets your visualization right the first time.
Model Context Protocol server exposing the ApexCharts ecosystem (charts, gantt, tree, sankey, grid, stock, maps) as tools for AI assistants
2026-11-17
Estrelas
—
Ferramentas
—
Disponibilidade
—
One MCP, seven products. Tools are namespaced per product (apexcharts_*, apexgantt_*, apextree_*, apexsankey_*, apexgrid_*, apexstock_*, apexmaps_*) so you can use any combination together.
Install
Pick your editor / client. You only need to do this once.
Hosted server (nothing to install)
The quickest way: point your client at the hosted server, https://mcp.apexcharts.com/mcp. It needs no Node.js and stays on the latest release.
Claude Code
claude mcp add --transport http apexcharts https://mcp.apexcharts.com/mcp
Any other client that accepts a remote MCP server URL (Streamable HTTP) connects the same way. To run the server on your own machine instead, use one of the local installs below.
Claude Code
claude mcp add apexcharts -- npx -y apexcharts-mcp
Every product exposes generate_config (build a valid config from a short spec) and validate_config (check a config against its skill's rules and return structured issues), plus get_reference to read that product's knowledge base on demand. The chart tools add apexcharts_list_types (a typed catalog of the 30 supported chart types, including the v6 additions violin, funnel, pyramid, gauge, unit, waffle, sunburst and histogram, the v7.1 additions waterfall, dumbbell, streamgraph and raincloud, the v7.6 addition icicle, and column, the synonym for bar that chart.type accepts since v7.9; each entry's bundle field says whether the default bundle has the type or names the add-on import a Tier 2 type needs); apexcharts_generate_config covers all 30 and apexcharts_validate_config checks against 40 rules. apexcharts_list_products is a meta tool that lists the products this server exposes, their tool names, and the upstream library version each product's guidance targets.
Limiting which products load
By default, all seven products' tools are registered. To load only a subset, set APEXCHARTS_MCP_PRODUCTS to a comma-separated list of product ids:
Valid ids: charts, gantt, tree, sankey, grid, stock, maps. Unknown ids are skipped with a stderr warning; the server still starts.
Running over HTTP
The install commands above run the server locally over stdio. To serve it over the network instead (for a shared team server, or a client that only takes a URL), start it with --http:
npx -y apexcharts-mcp --http --port 3000
It speaks Streamable HTTP at /mcp and answers a dependency-free health check at /healthz. Connect a client to it:
claude mcp add --transport http apexcharts http://localhost:3000/mcp
The server is stateless and answers every request with plain JSON. Every tool is a quick read-only call, so it keeps no sessions and opens no long-lived streams: GET and DELETE on /mcp return 405, which the spec defines as "this server offers neither". Nothing outlives a single request, so it runs behind any load balancer without sticky sessions or a raised idle timeout.
Setting
Default
Meaning
--port or PORT
3000
Port to listen on
--host or APEXCHARTS_MCP_HOST
127.0.0.1
Address to bind. Use 0.0.0.0 in a container
APEXCHARTS_MCP_ALLOWED_HOSTS
localhost,127.0.0.1,[::1]
Hostnames /mcp answers for (DNS-rebinding defence), or *. Set it to your public hostname when exposing the server
APEXCHARTS_MCP_ALLOWED_ORIGINS
none
Browser origins that may call /mcp (CORS), or *. Requests without an Origin header, which is every IDE and desktop client, are always accepted
APEXCHARTS_MCP_PRODUCTS
all
Same as in stdio mode
Request bodies are capped at 1 MiB. Each request writes one JSON line to stdout naming the JSON-RPC method and tool (never the arguments); diagnostics go to stderr. SIGTERM lets in-flight requests finish before exiting.
A Dockerfile builds a production image that listens on port 3000 inside the container:
apextree-skill: data format, graph API, framework wrappers
apexsankey-skill: data format, styling/interaction, framework wrappers
apexgrid-skill: columns/templates, data pipeline, sort/filter, state and interaction features (row pinning/reordering, undo-redo, validators, localization), framework integration, vanilla JS
apexstock-skill: OHLC data format, technical indicators, streaming/appendData, trading overlays, the analysis workspace (range statistics, drawdown, measurements, comparison), state and export, theming, framework wrappers
apexmaps-skill: series data formats, geo joins, geometry registry, projections, scales, drilldown, framework wrappers
They're regular dependencies: to pick up upstream improvements, bump the version in this repo's package.json and in the product's packages/mcp-<id>/package.json (see CLAUDE.md). Each skill repo is the source of truth for its own docs.
Contributing
For working on apexcharts-mcp itself.
git clone https://github.com/apexcharts/apexcharts-mcp.git
cd apexcharts-mcp
npm install
npm run build
The build runs tsc -b across all workspaces, then bundles src/index.ts (plus all workspace packages) into a single dist/index.js via esbuild. Skill packages stay external because they resolve file paths via import.meta.url.
Point your client at the local build instead of the published package:
claude mcp add apexcharts -- node /absolute/path/to/apexcharts-mcp/dist/index.js
Common scripts:
npm run dev # tsc -b --watch
npm test # vitest
npm run typecheck # tsc -b
npm run clean # remove all dist/ output
Keeping the bundled knowledge base honest (see CLAUDE.md for the full loop):
npm run check:versions # is any upstream library ahead of what its skill was verified against?
npm run check:chart-types # hard gate: every chart type the library ships is documented and supported
npm run check:surface-delta # what shipped since the pin that the docs never mention
npm run verify:skills # signal: doc examples referencing names the types don't have
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Apexcharts?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Apexcharts precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Apexcharts usa?
Apexcharts roda localmente via stdio.
Quando Apexcharts foi verificado pela última vez?
Última verificação: 2026-11-17. Model Context Protocol server exposing the ApexCharts ecosystem (charts, gantt, tree, sankey, grid, stock, maps) as tools for AI assistants