Quick Chart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Optional environment setting (development or production) | development |
| QUICK_CHART_DRAW_URL | No | Optional quick chart draw URL | |
| NEED_INSTALL_QUICK_CHART | No | Optional flag to determine if quick chart needs to be installed (true or false) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| GetChartImgLinkC | To draw chart and get chart image link by parameters, and parameter grammar follows Quick Chart API (quickchart.io). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| GetChartImgLink-examples |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as generating chart image links using Quick Chart API parameters.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'GetChartImgLink' follows a clear verb_noun pattern, and there are no other tools to compare or create inconsistency with.
A single tool is too few for a chart generation server, as it lacks basic operations like creating, updating, or deleting charts, or handling different chart types or configurations. This minimal set limits functionality and forces agents to rely solely on this one tool for all chart-related tasks.
The tool set is severely incomplete for a chart generation domain. It only provides a way to get chart image links, missing essential operations such as creating, listing, updating, or deleting charts, and lacks support for managing chart templates or configurations, which are typical in such systems.