MCP server

Website reference for agent tools 0.2.3. The currently recorded tested library pairing is 1.1.5; the latest verified public Core distribution is 1.1.5. Core 1.1.5 is published through the verified release channels. Run wcc version --json or read wcc://version to identify your installed runtime. This website derives the reference heading and distribution guidance from its release manifest while preserving the pinned source document. Historical output below retains its original version and values; it is not proof of a newer release.

#Install CLI and MCP

Public agent tools 0.2.3, tested with Library 1.1.5; available from the versioned GitHub release and npm. The command below installs both the current Core runtime and the tools. Premium is a separately supplied runtime; it is not included in either public archive. Premium customers replace the Core installation command with their private complete library package; see the Premium setup section in the MCP guide.

npm install west-coast-charts@1.1.5
npm install west-coast-charts-agent@0.2.3
npx --no-install wcc --help
npx --no-install wcc-mcp --help

Agent-tool source and release. Agent archive SHA-256: ca2c7af4a00d69f2d463d310139480aca8cef4e06163897d86b1ed90da4e7865. Read wcc://version after connecting to verify the resolved library, validator and description providers.

Use npm install 'west-coast-charts@>=1.1.1 <1.2.0' west-coast-charts-agent@0.2.3 for the supported 0.2.3 / Core 1.1.x range. Verify availability and artifact checksums in the release metadata; see the root README for installation. The executable is wcc-mcp; wcc-mcp --help and wcc-mcp --version terminate without starting the server. No unpublished @westcoastcharts/mcp npm package is required.

#Local stdio

Use an absolute executable path in your MCP client:

{"mcpServers":{"west-coast-charts":{"command":"/absolute/project/node_modules/.bin/wcc-mcp","args":[]}}}

For Premium, install the separately obtained complete matching library, or select a separate extraction with WCC_LIB_ROOT. Supply WCC_LICENSE_KEY through the client's private environment. Do not put a key in public configuration or source control. No key is needed for free charts. WCC_EVALUATION=1 explicitly enables watermarked Premium evaluation only when the Premium runtime is present; a supplied invalid key is still rejected.

#Tools

• render_chart: real SVG or PNG plus the verification table.
• validate_chart: selected runtime’s matching validator with errors, warnings and fix suggestions.
• describe_chart: the actual wcc-describe/1 model, with tableSource: "describe".
• get_schema: bounded slices of the matching options schema.
• list_chart_types, list_examples, get_example: discover supported types and JSON examples.

Examples and typed options may include Premium vocabulary without including Premium implementation. Missing runtime modules fail explicitly. No production validator or table stubs are used. Resources include tool guides, errors, version metadata, recent renders, and library documentation when the selected runtime contains it. Prompts: pick_chart_type and build_dashboard.

#HTTP (optional)

wcc-mcp --transport http starts the optional Streamable HTTP service. Read wcc-mcp --help for host, port, origin and bearer-token options. Keep it on loopback unless you deliberately configure authentication and deployment controls; this archive does not deploy a hosted service. Tool requests are JSON-only and do not evaluate user JavaScript. Version 0.2.2 requires explicit issuer, audience and scopes for JWKS authorization; see HTTP security. SDK 1.32.2 negotiates MCP 2025-11-25 and older supported revisions, not MCP 2026-07-28.

#Distribution status

The supported release format is the single agent .tgz, with native PNG dependencies selected by npm for the installation platform. The repository's empty MCP registry package list describes that separate registry; it does not establish npm availability. Each release has its own immutable version and artifact metadata; the 0.2.1 release is not rewritten by 0.2.2. MCPB metadata is a template, not a downloadable bundle; no zero-hash or nonexistent bundle is advertised. Use the tested stdio executable in desktop clients.

#Premium licence and runtime

The public agent tools contain no Premium renderer or add-on. A Premium or trial key does not install those modules. Use the complete library package from your private purchase confirmation or 30-day trial, then install the public tools in the same project:

# Use the complete library downloaded from your private purchase/trial page.
# The public Core archive has the same package name, but excludes Premium.
npm install ./west-coast-charts-1.1.5.tgz
npm install west-coast-charts-agent@0.2.3
npx --no-install wcc version --json

The tools resolve the installed west-coast-charts package. A separate WCC_LIB_ROOT is unnecessary in this layout; it can explicitly select another extracted complete package. Confirm the actual library version in wcc version --json or the MCP wcc://version resource. Tool version 0.2.3 is separately versioned and tested with Library 1.1.5.

#Connect a Premium customer's agents

Use the executable's actual absolute path in your MCP client's private settings. The JSON below is an illustrative client configuration, not a claim that every client uses this exact settings format:

{
  "mcpServers": {
    "west-coast-charts-premium": {
      "command": "/absolute/project/node_modules/.bin/wcc-mcp",
      "args": [],
      "env": {
        "WCC_LICENSE_KEY": "<your private Premium or trial key>"
      }
    }
  }
}

Replace the path and placeholder in your private client settings. Prefer the client's secret facility if it provides one. Never commit the key, paste it into a shared chart spec or put it in command-line arguments. MCP 0.2.3 reads WCC_LICENSE_KEY; it does not read WCC_LICENSE_KEY_FILE. The CLI additionally supports --license-key-file. A domain-bound key must permit headless.wcc.invalid, the headless renderer's host; this check is not bypassed.

After connecting, read wcc://version, list_chart_types and get_schema. Then validate_chart → render_chart → describe_chart uses the same separately installed Premium runtime, including the loaded Quint, Vitals Clock and Practice Schedule modules. Require validator: "e1" and tableSource: "describe". Missing modules and invalid/expired keys are explicit errors; they must not silently fall back to placeholders.

#Review Premium before starting a trial

Read the public Premium examples, complete example directory, and prices, annual terms and support scope without a key. These show the product and its configuration; viewing them does not issue a licence or install the Premium runtime. To test your own project, obtain the complete package and key through the card-free 30-day trial or your purchase confirmation. The public agent package alone cannot run Premium charts.

#Repeat a bounded Premium check

After the complete-package installation above, save the key in a private file outside the project. Use its actual path below; do not put the key itself in the command.

npx --no-install wcc examples get quint-timeline --spec-only > quint.json
npx --no-install wcc chart validate quint.json --json
npx --no-install wcc chart table quint.json --license-key-file /private/path/premium.license --json
npx --no-install wcc chart render quint.json --license-key-file /private/path/premium.license > quint.svg

Repeat with example ID schedule-demo. With MCP, call get_example with the ID, pass its structuredContent.spec to validate_chart, render_chart and describe_chart, and inspect their returned data. Require validator e1, tableSource: "describe" and, for the licensed render, meta.licensed: true. The CLI table is the describe model directly; in MCP it is structuredContent.table.

The following synthetic fixtures are public and pinned to the checked tool source. Compare them with the installed example before using these expected results:

#What the existing check establishes

An independent check on 28 October 2026 covered a separately pinned package pair. It does not establish acceptance of the currently listed agent tools 0.2.3 and Library 1.1.5; repeat the checks above for that pair. It installed the packages outside all workspaces with an empty user profile and module-resolution guards. All 39 shipped Core and Premium fixtures passed MCP validation, SVG rendering and describe checks, with matching rendered and described tables. The fixtures represented all 13 Premium families; one representative per family also produced a verified PNG. The Quint CLI key-file path and the concrete fixture values above passed against that same customer layout.

There were 56 rejection checks: expired and foreign-signed test keys were rejected by both render and describe for all 13 Premium families (52 checks), plus four Quint Timeline checks confirmed that evaluation mode did not bypass those invalid keys. These tests used dedicated local acceptance fixtures, not customer keys or live payment requests.

This is a bounded headless integration check, not exhaustive coverage of every chart option or a certification of browser-layout parity, performance, your data or your application's suitability. It does not test every chat viewer or recommend a commercial plan. CLI reference · Quint guide · Schedule guide.

#Evaluation and hosting

No key is needed for Core. To evaluate an installed Premium runtime without a key, explicitly enable WCC_EVALUATION=1 (or CLI --evaluation); the output is watermarked. A supplied invalid or expired key remains rejected even in evaluation mode. An issued 30-day trial key can also be used privately through WCC_LICENSE_KEY for its stated term.

If a chat or artifact viewer cannot execute JavaScript, the CLI and MCP can render SVG or PNG for display as an image. That output does not require the viewer to load a chart CDN; it does not provide browser interactivity.

The installable MCP server runs on the customer's computer or infrastructure. A hosted multi-tenant Premium MCP service is not included or automatically deployed. The optional HTTP transport requires deliberate authentication, origin and deployment controls before remote access. Do not expose an unauthenticated service or share the private purchase/trial access link. Tool setup and transport options.