Can I use Vega-Lite as a CLI?

Yes. KosmoKrator exposes a Vega-Lite CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Vega-Lite through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Vega-Lite tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Vega-Lite credentials stored?

Vega-Lite credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Vega-Lite MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

rendering

Vega-Lite MCP, CLI, and Lua Integration for AI Agents

Vega-Lite integration docs for AI agents: MCP gateway setup, Vega-Lite CLI commands, Lua API reference, credentials, and function schemas.

1 functions 0 read 1 write No credentials auth

Submit Vega-Lite feedback View package source

Vega-Lite for agents

No credentials required; available in web and CLI hosts when runtime dependencies are installed.

Use this integration from Lua code mode, the headless integrations CLI, or the KosmoKrator MCP gateway. The same package metadata powers all three surfaces.

Machine-Readable Metadata

integration_slug: vegalite
route_slug: vegalite
package: vegalite
auth_strategy: none No credentials
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true
supports_multi_account: false

Quick Links

Lua APIAgent-facing namespace and function reference. Vega-Lite CLIHeadless setup and direct function calls. Vega-Lite MCPMCP gateway setup for external clients. Submit feedbackReport missing tools, auth problems, wrong docs, or runtime issues. ContributeAdd tools or improve metadata in the integrations repo.

Vega-Lite MCP Client Matrix

Use these pages when a specific agent client or framework needs copy-pasteable MCP setup for Vega-Lite.

Vega-Lite CLI Matrix

Use these pages for direct Vega-Lite CLI workflows in scripts, CI, cron, and agent wrappers.

CI Vega-Lite CLI for CI. Cron Jobs Vega-Lite CLI for cron jobs. Shell Scripts Vega-Lite CLI for shell scripts. Headless Automation Vega-Lite CLI for headless automation. Coding Agents Vega-Lite CLI for coding agents.

Runtime Requirements

Name	Type	Description
`node`	binary	Node.js is required to render Vega-Lite charts.

Function Catalog

Function	Type	Parameters	Description
`vegalite.render_vegalite`	Write `write`	3	Render a Vega-Lite visualization to a PNG image. Pass a complete Vega-Lite JSON specification and get back a markdown image embed. IMPORTANT: Always use inline data with "data": {"values": [...]}. Never use "data": {"url": "..."}. Example spec: { "$schema": "https://vega.github.io/schema/vega-lite/v5.json", "data": {"values": [ {"category": "A", "value": 28}, {"category": "B", "value": 55}, {"category": "C", "value": 43} ]}, "mark": "bar", "encoding": { "x": {"field": "category", "type": "nominal"}, "y": {"field": "value", "type": "quantitative"} } } Supported mark types: bar, line, point, area, rect, circle, square, arc, text, tick, rule, trail, boxplot. Always include "type" in encoding channels: "quantitative", "nominal", "ordinal", or "temporal".