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: generate_chart creates a chart, while download_chart saves it to a file. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun pattern (generate_chart, download_chart) with clear, descriptive names that align well with their functions.
With only 2 tools, the server feels thin for a chart generation domain. While it covers basic creation and downloading, typical charting needs might include configuration, formatting, or data manipulation tools that are missing here.
The toolset is severely incomplete for chart generation. It lacks essential operations like configuring chart types, setting data, adjusting styles, or managing templates, which are core to the domain and would cause agent failures in complex tasks.