QuickChart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| generate_chartC | Generate a chart using QuickChart |
| download_chartC | Download a chart image to a local file |
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
The two tools have clearly distinct purposes: 'download_chart' handles saving a chart to a file, while 'generate_chart' focuses on creating the chart itself. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun pattern with snake_case naming: 'download_chart' and 'generate_chart'. The naming is predictable and uniform across the set.
With only 2 tools, the server feels thin for a chart generation domain. A more complete surface might include tools for chart customization, listing chart types, or managing chart data, making this count borderline insufficient.
The tool set is severely incomplete for chart generation. It lacks operations for updating or deleting charts, configuring chart parameters, or retrieving chart metadata, which are common needs in this domain and could lead to agent failures.