A
licenseC
qualityF
maintenanceAn MCP server for generating customizable data visualizations using QuickChart.io, supporting multiple chart types and Chart.js configuration.
2
207 npm
159
MIT
Quick-Chart
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Quick-Chartcreate a bar chart showing monthly sales for 2024"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
图表工具服务 Quick Chart
一个基于Model Context Protocol (MCP)的服务器，提供与Quick Chart交互的标准化接口，支持图表生成和管理。 A server based on Model Context Protocol (MCP), providing a standardized interface for interacting with Quick Chart and supporting chart generation and management.## 工具列表 Tool List
本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。 本MCP服务封装下列工具，可让模型通过标准化接口调用以下功能。
工具 Tool | 描述 Description |
GetChartImgLink | To draw chart and get chart image link by parameters, and parameter grammar follows Quick Chart API (quickchart.io). |
检查服务 ## Inspector
工具在线测试： https://mcp.xiaobenyang.com/inspector/1777316659546115
Online Tool test https://mcp.xiaobenyang.com/inspector/1777316659546115
Related MCP server: OpenAPI MCP Server
服务配置 MCP Server Config
如何获取 XBY-APIKEY ？ How to get XBY-APIKEY ?
访问小笨羊科技网站 https://xiaobenyang.com，注册用户即可获得APIKEY Visit XiaoBenYang website https://xiaobenyang.com, register and get the APIKEY.
SSE
{
"mcpServers": {
"图表工具服务": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "sse",
"url": "https://mcp.xiaobenyang.com/1777316659546115/sse"
}
}
}STREAMABLE HTTP
{
"mcpServers": {
"图表工具服务": {
"headers": {
"XBY-APIKEY": "<YOUR_XBY_APIKEY>"
},
"type": "streamable_http",
"url": "https://mcp.xiaobenyang.com/1777316659546115/mcp"
}
}
}STDIO
{
"mcpServers": {
"图表工具服务": {
"command": "npx",
"args": [
"-y",
"xiaobenyang-mcp"
],
"env": {
"XBY_APIKEY": "<YOUR_XBY_APIKEY>",
"mcpId": "1777316659546115",
},
"transport": "stdio"
}
}
}
Available Tools
1 toolGetChartImgLinkGetChartImgLinkC
To draw chart and get chart image link by parameters, and parameter grammar follows Quick Chart API (quickchart.io).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| json | No |
TDQS
C2.4/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions the tool draws a chart and returns an image link, but doesn't disclose behavioral traits like whether this requires external API calls, rate limits, authentication needs, error conditions, or what format the link returns in. The description adds minimal behavioral context beyond the basic operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is appropriately concise with two clauses that directly address purpose and parameter usage. It's front-loaded with the main action and avoids unnecessary words, though it could be slightly more structured by separating usage notes from purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no annotations, no output schema, and minimal parameter documentation, the description is incomplete. It covers the basic operation but lacks details on behavior, return values, error handling, and comprehensive parameter guidance, making it inadequate for reliable agent use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 1 parameter with 0% description coverage. The description adds that parameters follow 'Quick Chart API (quickchart.io)' grammar, which provides some semantic context about the expected format, but doesn't explain what the 'json' parameter should contain, what chart types are supported, or provide examples. This partially compensates for the schema gap but remains insufficient.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool's purpose: 'draw chart and get chart image link by parameters', which is a clear verb+resource combination. However, it's somewhat vague about what kind of chart or what specific resources are involved, and with no sibling tools to distinguish from, it lacks differentiation context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It mentions that 'parameter grammar follows Quick Chart API (quickchart.io)', which hints at context but doesn't explicitly state when this tool is appropriate or what prerequisites exist for its use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
GetChartImgLink
TDQS
C2.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to confuse it with. The tool's purpose is clearly defined to generate chart images via the Quick Chart API.
Naming Consistency5/5
Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate. The tool name 'GetChartImgLink' follows a clear verb_noun pattern.
Tool Count2/5
A single tool is too few for a chart generation server, as it lacks basic operations like creating different chart types, customizing parameters, or managing charts, which limits functionality and scope. This feels thin and incomplete for the domain.
Completeness1/5
The tool set is severely incomplete for chart generation, offering only one tool to get a chart image link without support for creating, updating, deleting, or customizing charts, which are essential operations in this domain. This will likely cause agent failures due to missing capabilities.
Maintenance
ActivityInactive
ResponsivenessNo issues
Related MCP Connectors
Bar-first MCP server for Tabula chart authoring, PNG rendering, and editor handoff.
Token-free MCP server for structured RevoGrid Core, Pro, and Enterprise knowledge retrieval.
MCP server for generating rough-draft project plans from natural-language prompts.
MCP server providing access to the Scorecard API to evaluate and optimize LLM systems.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA server that implements the Model Context Protocol (MCP) with StreamableHTTP transport, enabling standardized interaction with model services through a RESTful API interface.301 npm2MIT
- AlicenseAqualityDmaintenanceThis Model Context Protocol (MCP) server provides powerful visualization tools using QuickChart.io APIs. With this MCP, AI assistants can create charts, diagrams, barcodes, QR codes, word clouds, tables, and more.1239 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that generates beautiful chart images from ECharts configurations, supporting various chart types with customizable dimensions.5 npm7MIT