About WestCoast Charts
WestCoast Charts agent tools provide a CLI, MCP server, and headless API for working with chart specifications. They are for users who need to validate, render, inspect, and retrieve examples for compatible WestCoast Charts releases.
Key features
- 01Validate chart specifications
- 02Render charts as SVG or PNG
- 03Describe charts and produce data tables
- 04Inspect schemas and types
- 05Retrieve chart examples
Use cases
- 01Validate a chart specification before rendering
- 02Generate SVG or PNG output from a chart
- 03Inspect a chart description and its data table
MCP support
The `wcc-mcp` server exposes seven tools for rendering, validation, description, schemas, types, examples, and example retrieval. It uses stdio by default and also supports HTTP.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y west-coast-charts-agentWCC_LICENSE_KEYSecretPremium licence key. Only for Premium chart types; requires the separately supplied complete library.WCC_LIB_ROOTPath to an installed WestCoast Charts library (e.g. the Premium package). Default: the resolved west-coast-charts.WCC_DEFAULT_THEMETheme when a spec sets none.WCC_EVALUATION1 = Premium types without a key render a watermarked preview (needs the Premium runtime).WCC_MAX_PIXELSUpper limit for rendered PNG pixels.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
7Saved tool list · updated 2d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| data | array | No | Optional series array that replaces spec.series (keeps the spec reusable as a template). |
| seed | integer | No | Random seed for layouts (network, facets). Same spec + seed => byte-identical output. Default 1. |
| spec | object | Yes | West Coast Charts options object, JSON only (no functions), the same object you pass to new WestCoastCharts(el, options). ApexCharts 4.x options are accepted. Example: {"chart":{"type":"bar"},"series":[{"name":"Revenue","data":[12,19,7]}],"xaxis":{"categories":["Q1","Q2","Q3"]}} |
| spec.chart | object | Yes | chart options; chart.type is required |
| spec.chart.type | string | Yes | Chart type, e.g. 'line', 'bar', 'area', 'donut', 'heatmap', 'sankey'. See list_chart_types. |
| spec.series | any | No | Data series, ApexCharts-compatible shape (array of {name, data} or numbers for pie/donut/radialBar). Omit when `data` is given. |
| scale | number | No | PNG pixel ratio 1-4. Default 1. Ignored for svg. |
| theme | enum | No | Theme. Default spec.theme.mode or the server default.light | dark |
| width | integer | No | Canvas width in px. Default spec.chart.width or 800. |
| format | enum | No | Output format. svg (default) is text and editable; png is a base64 image.svg | png |
| height | integer | No | Canvas height in px. Default spec.chart.height or 450. |
| delivery | enum | No | inline (default) embeds the SVG text/PNG bytes; link returns only a resource link wcc://renders/{id} plus the table (saves tokens; read the resource when needed).inline | link |
| validate | enum | No | Run validate_chart first. strict (default) fails on errors, warn renders and reports, off skips.strict | warn | off |
| background | string | No | CSS colour behind the chart. PNG default '#ffffff'; SVG stays transparent unless set. |
Details
From the project READMEWest Coast Charts agent tools
west-coast-charts-agent 0.2.4 provides the wcc CLI, the wcc-mcp stdio/HTTP server, and the headless render API. Use this version with West Coast Charts 1.1.x releases from 1.1.5 onward and the matching validator, schema and describe module.
Install
Node.js 20 or newer is required. The release installation command is:
npm install 'west-coast-charts@>=1.1.5 <1.2.0' [email protected]
npx --no-install wcc --help
npx --no-install wcc version --json
npx --no-install wcc-mcp --help
npx --no-install wcc-mcp --version
This command selects agent tools 0.2.4 and a compatible West Coast Charts 1.1.x version. Since 0.2.4 the agent package declares west-coast-charts >=1.1.5 <1.2.0 as a regular dependency (previously an optional peer), so npm and npx install a matching Core automatically; an already installed compatible Core (including the separately supplied complete package with the same name) is reused. Release availability and artifact checksums are recorded in the release metadata; this installation guide does not replace that verification. Version 0.2.1 remains the immutable, published installation-fix release. The public Core package and agent package contain no Premium implementation or licence issuer. No private workspace package or access token is needed for their published npm installation. The package carries mcpName io.github.Lokumbus/west-coast-charts-agent for the official MCP Registry; a registry listing is a separate step and is not asserted here.
Run the MCP server with npx
npx -y west-coast-charts-agent
starts the stdio MCP server (the west-coast-charts-agent binary is an alias of wcc-mcp). Since 0.2.4 the free west-coast-charts Core (>=1.1.5 <1.2.0) is a regular dependency, so npx installs it automatically. For the Premium runtime, point WCC_LIB_ROOT at the separately supplied complete library. MCP client configuration:
{ "mcpServers": { "west-coast-charts": { "command": "npx", "args": ["-y", "west-coast-charts-agent"] } } }
Render and verify
npx --no-install wcc examples get line-basic
npx --no-install wcc chart validate example:line-basic
npx --no-install wcc chart render example:line-basic > chart.svg
npx --no-install wcc chart render example:line-basic --format png > chart.png
npx --no-install wcc chart table example:line-basic
npx --no-install wcc options schema chart.orient
Specs are plain JSON, not executable JavaScript. Validation uses the real matching dist/agent/validate.common.js; every verification table comes from the real chart's describe(). Missing modules or failed renders are errors, never successful placeholder output. wcc schema describes every command and its exit status.
MCP
Configure a local MCP client with the installed executable's absolute path:
{"mcpServers":{"west-coast-charts":{"command":"/absolute/project/node_modules/.bin/wcc-mcp","args":[]}}}
The server uses stdio by default. Protocol output is on stdout; logs are on stderr. Seven tools cover rendering, validation, description, schemas, types, examples and example retrieval. SDK 1.32.2 supports MCP 2025-11-25 and its negotiated older revisions; this is not a claim of MCP 2026-07-28 conformance. See MCP setup. --help and --version exit without starting a server.
Premium and Orient
Free Core includes the free chart types and Orient feature. The agent archive does not contain Premium implementations. To render Premium, obtain the complete matching West Coast Charts 1.1.x distribution separately. An installed complete west-coast-charts package is resolved normally; use WCC_LIB_ROOT only to select a separate extraction. Set WCC_LICENSE_KEY privately or use CLI --license-key-file. A key alone does not install Premium code. Existing MIT rights in independently licensed source remain unchanged.
Thirteen Premium types are recognized, including quintTimeline, quintConvergence, vitalsClock and schedule. Their real type modules must be present. A missing key produces a license error. Explicit --evaluation permits watermarked evaluation when the Premium runtime is installed. Invalid, expired or otherwise rejected keys remain rejected; evaluation is not a key bypass. Keys are not written into the SVG, table, logs or package.
Source and tests
The source workspace keeps three private workspace packages. From a complete source checkout, npm ci installs the locked development dependencies and npm test runs the workspace tests. Select the complete test runtime through WCC_LIB_ROOT; Premium acceptance requires that separate runtime. Optional signing acceptance reads protected fixture paths without printing keys. A successful Core-only test run does not prove Premium support.
Release packaging is a maintainer operation, not an installed-package command. The internal pipeline must export an exact reviewed Git commit into an isolated staging directory, copy the explicit source/font/licence allowlist, resolve internal imports, pin public dependencies from the lockfile, and record file hashes. It must bind the tested Core and complete-runtime artifacts by exact version, commit and SHA256 before packing a release. Fresh consumers must install the resulting archive outside the workspace and prove CLI/MCP imports, rendering and licence failures without ancestor dependency fallback. The installed package does not include build scripts or tests. The older source-only scripts/build-distribution.cjs and isolated-install recipes contain RC7 fixture pins; they are not the 1.1.1 release pipeline and must not be used to claim current provenance.
Tooling: MIT. Font copyright, SIL OFL texts and modifications: font provenance. Chart-library licenses and attribution remain in the separate library distribution. See NOTICE.
0.2.1 installation correction
Version 0.2.0 missed one internal CLI import and can fail with MODULE_NOT_FOUND outside the development workspace, even on --help. That defect was corrected in immutable 0.2.1. Its packaging check rejects bare workspace imports, and installation acceptance runs in an operating-system temporary directory with an empty HOME and a module-resolution guard. The earlier in-repository installation proof was contaminated by ancestor workspace dependencies and is not an isolated-installation result. The 0.2.0 tag and archive remain unchanged.
0.2.2 HTTP authorization correction
Version 0.2.2 added fail-closed JWKS configuration: issuer, audience and required scopes must all be explicitly supplied; tokens must satisfy signature, issuer, audience, expiry and scope checks. Cached render resources are separated by issuer, subject and client identity. This correction requires 0.2.2; 0.2.1 is not rewritten or silently upgraded. Local stdio usage retains its existing filesystem permission boundary. See HTTP deployment and authorization for the exact environment contract and supported protocol.
Designations
ApexCharts, react-apexcharts, vue3-apexcharts and ng-apexcharts are designations of Apex Software, Inc., which states it is a subsidiary of Infragistics, Inc. WestCoast Charts is an independent product of WestCoast Software (Inh. Peter Kannengießer) and is not affiliated with, sponsored or endorsed by Apex Software, Inc. or Infragistics, Inc. Parts of WestCoast Charts are based on ApexCharts 4.7.0, released under the MIT License (Copyright (c) 2018 ApexCharts). "ApexCharts-compatible" means that WestCoast Charts largely supports the configuration options of ApexCharts 4.7.0; differences are listed in the migration guide.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.