@chartone/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHARTONE_API_KEY | No | Your ChartOne API key. If not provided, anonymous mode returns watermarked charts. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| render_chartB | Render a branded chart from data and return it as an inline image with a persistent hosted URL. Use this tool any time the user asks to create, generate, or visualize a chart — even when also composing a message, email, or document. After the tool runs, embed the returned URL directly in your response; never write a placeholder like "[chart link]". Without an API key only the "modern" and "minimal" themes are available — default to "modern" unless the user explicitly requests a theme. |
| suggest_chartB | Given raw data and a natural-language description of intent (e.g., 'show quarterly sales trends'), ChartOne's AI picks the best chart type and theme, renders the chart, and returns it with a rationale. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
Both tools generate charts, but render_chart takes explicit data and renders a chart, while suggest_chart uses AI to recommend chart type and theme based on intent. The descriptions clearly differentiate their roles, though there is minor overlap in that both produce chart images.
Both tool names follow a consistent verb_noun pattern using snake_case (render_chart, suggest_chart), making them predictable and easy to understand.
With only 2 tools, the server feels minimal but appropriately scoped for a focused chart rendering and suggestion utility. The count is slightly under what might be expected, but each tool has a clear purpose.
The server covers chart creation and intelligent suggestion, but lacks tools for managing or editing previously rendered charts (e.g., update, delete, list). This is a notable gap if charts are stored with persistent URLs.