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.

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.

Agent Surfaces

Vega-Lite CLIHeadless setup, JSON output, direct function calls. Vega-Lite MCPExpose selected tools to local MCP clients. Vega-Lite LuaAgent-facing namespace and Lua reference. FeedbackReport missing tools, auth issues, or bad metadata.

Machine-Readable Metadata

integration_slug: vegalite
route_slug: vegalite
package: vegalite
auth_strategy: none
cli_setup_supported: true
cli_runtime_supported: true
mcp_gateway_supported: true
lua_supported: true

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".