MCP server

Connect once

Choose your coding agentLOCAL / VERSION-MATCHED

Codex

codex mcp add sixtyfold -- npx -y @sixtyfold/mcp@next

@sixtyfold/mcp is Sixtyfold’s optional local Model Context Protocol server. It gives compatible coding tools a compact, searchable view of the exact public API shipped with the package, plus deterministic integration recipes and performance checks.

It is developer tooling—not part of a chart. Installing or connecting it does not add code to @sixtyfold/line, @sixtyfold/stock, a framework adapter, or your browser bundle.

Connect an MCP host

Add a local stdio server to the MCP configuration used by your editor or coding tool:

{
  "mcpServers": {
    "sixtyfold": {
      "command": "npx",
      "args": ["-y", "@sixtyfold/mcp@next"]
    }
  }
}

Restart or reload the host after saving its configuration. The explicit next tag follows the reviewed 1.0.0 release-candidate channel.

You can install the executable explicitly instead:

pnpm add --global @sixtyfold/mcp@next
sixtyfold-mcp

The executable writes MCP JSON-RPC messages to standard output. Do not wrap it in a shell command that prints banners or debug messages to standard output.

Tools

Tool	What it provides
`list_packages`	Independent packages, versions, and public entry points
`inspect_component_api`	Focused search over exact exported symbols, members, signatures, and documented failure contracts
`recommend_packages`	The smallest engine, framework, theme, and SSR package set
`generate_integration`	Lifecycle-safe framework code, with optional row/column data-shape conversion into typed arrays
`validate_chart_options`	Deterministic top-level line or stock option checks
`recommend_performance_settings`	Grounded render-mode, level-of-detail (LOD), and typed-array starting points
`diagnose_chart`	Focused checks for lifecycle, LOD, buffers, memory, and rendering symptoms

recommend_performance_settings and diagnose_chart require component: "line" | "stock" and reject unsupported identifiers instead of guessing.

Every tool declares itself read-only, non-destructive, and idempotent.

Resources and prompts

Read-only resources give hosts browsable context:

Resource	URI
`package-catalog`	`sixtyfold://catalog/packages`
`package-api`	`sixtyfold://api/{packageName}`
`performance-guide`	`sixtyfold://guides/performance`
`data-ownership-guide`	`sixtyfold://guides/data-ownership`

Guided prompts cover the common working sessions:

Prompt	Purpose
`add-sixtyfold-chart`	Add a chart to an existing app with correct lifecycle and data ownership
`tune-sixtyfold-performance`	Tune render mode, LOD, and data transfer for a measured workload
`review-sixtyfold-integration`	Review an existing integration against the ownership and lifecycle rules

The API inventory is generated from the same TypeScript declarations shipped by the component packages. The release build fails if the catalog differs from those public entry points.

Example requests

After the host reports that the Sixtyfold server is connected, try:

Add a worker-first Sixtyfold line chart to this React view. Keep my source
buffers readable after setData and clean up the chart when the view unmounts.

Generate a Vue line chart for object rows with ISO timestamps in recordedAt
and numeric temperature and humidity fields. Expect about two million rows.

Review these LineChart options and recommend starting LOD values for four
five-million-point series. Explain which numbers I should benchmark locally.

Why does this chart change slightly after a zoom animation settles? Inspect the
current LOD and viewport APIs before suggesting a fix.

The MCP host decides whether and when to call a tool. Treat generated code as a reviewable starting point and keep TypeScript compilation, tests, and workload measurements in the normal development loop.

Privacy and security

Version 1 uses local stdio only. The Sixtyfold server has no account, API key, telemetry, analytics, remote documentation fetch, activation request, or runtime phone-home. It does not receive customer chart data unless the MCP host chooses to include that data in a tool argument.

Your MCP host and its model have their own data-handling rules. Review those separately before sending proprietary source, datasets, or credentials. Keep MCP server configuration in developer tooling; do not expose the process as a public HTTP endpoint.

Inspect and verify

Use the official MCP Inspector against a locally installed executable:

npx @modelcontextprotocol/inspector sixtyfold-mcp