Chartly

@Chartly render a bar chart showing our API response times by endpoint: /users 120ms, /orders 340ms, /products 95ms, /search 580ms

I've rendered a bar chart visualizing your API response times. The chart shows /search as your slowest endpoint at 580ms, followed by /orders at 340ms, /users at 120ms, and /products at 95ms. The image has been generated as a PNG and is ready for download. This is a one-time render—no permanent URL was created, so the chart exists only in this response.

This example uses the ephemeral render tool, ideal for quick visualizations in chat without cluttering your Chartly account. The AI translates your data into a Chart.js config behind the scenes. No permanent resource is created, so there's nothing to clean up later.

@Chartly create a permanent chart of our monthly revenue: Jan $45k, Feb $52k, Mar $61k, Apr $58k, May $67k as a line chart with a gradient fill

I've created a permanent Chartly chart showing your monthly revenue trend from January through May. The line chart uses a gradient fill to emphasize growth from $45k to $67k. Your permanent chart URL is chartly.io/c/abc123xyz. Important: this chart is now permanent and cannot be deleted through Chartly's API—you'll need to contact their support if you want it removed.

This demonstrates the permanent chart creation tool, which generates a shareable URL. The critical trade-off: Chartly provides no delete endpoint, so every chart you create persists indefinitely in your account. Use this only when you need a stable, long-lived URL for embedding or sharing.

@Chartly fetch the image for chart ID c7f3a9b2 and analyze whether the trend suggests we should increase our infrastructure budget next quarter

I've retrieved the chart image for c7f3a9b2, which shows your server CPU utilization over the past six months. The trend line reveals a steady 8% month-over-month increase, with April and May both exceeding 75% average utilization. Given this trajectory, you're likely to hit capacity constraints by Q3. I'd recommend budgeting for additional infrastructure—either horizontal scaling or instance upgrades—to maintain headroom before you encounter performance degradation.

This example pairs Chartly's image retrieval with AI reasoning. The MCP fetches the chart as PNG or SVG, then the AI analyzes the visual data to answer your strategic question. Requires you already have a permanent chart ID from a previous creation step.

When Chartly beats manual screenshot workflows for recurring dashboards

A 6-person engineering team sends a weekly metrics email to stakeholders—deploy frequency, error rates, test coverage. Before Chartly, someone manually screenshotted Datadog or Grafana every Friday. With Chartly's Render Chart tool, the team's Slack bot now generates fresh Chart.js PNGs on demand and drops them into the email template. No permanent URLs needed, no API quota wasted on undeletable resources. The trade-off: if your charts need live data from external APIs, you're still writing the Chart.js config by hand or piping it from another MCP. Chartly just renders what you give it. If your team already has the data pipeline and needs a no-fuss image generator for recurring reports, Chartly closes the loop.

Why Chartly's permanent URLs work for one-off customer charts

A 3-person support team at a SaaS startup occasionally needs to send customers a visual breakdown of their usage—API calls over time, feature adoption by user cohort. The Create Permanent Chart tool gives them a shareable Chartly URL that lives forever, no hosting required. The customer clicks the link, sees the chart, case closed. The downside: those URLs never expire and Chartly has no delete endpoint, so you're creating permanent internet artifacts. If you're generating hundreds of charts a month, you'll pollute your Chartly account. But for 5-10 high-touch customer conversations a quarter, the permanent URL is faster than emailing a PNG or spinning up a custom dashboard. If your volume is low and the chart is worth keeping, Chartly's the call.

When Chartly's SVG output beats static PNG for design handoffs

A 4-person product design team prototypes data-heavy UI in Figma but needs real chart visuals for investor decks and product specs. The Render Chart tool outputs SVG, so designers can drop the file into Figma, tweak colors or labels, and keep the vector fidelity. No rasterized screenshots, no re-exporting from a BI tool every time the data changes. The catch: you're still writing Chart.js config JSON, which means someone on the team needs to know the Chart.js API or copy-paste from examples. If your designers are comfortable with JSON or you have a dev who can template the configs, Chartly's SVG output is cleaner than screenshot workflows. If your team is non-technical and the chart complexity is high, a dedicated BI tool with a GUI is the better fit.