MCP Server Chart

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP Server Chart?

MCP Server Chart is a Model Context Protocol server designed for generating various types of charts using AntV. It provides a flexible and efficient way to create visual data representations.

How to use MCP Server Chart?

To use MCP Server Chart, configure the server in your application by adding the server configuration in JSON format. You can then generate charts by calling the respective functions for the type of chart you need.

Key features of MCP Server Chart?

  • Supports over 15 types of charts including area, bar, line, pie, and more.
  • Generates chart images that can be easily integrated into applications.
  • Built with TypeScript for better development experience and type safety.

Use cases of MCP Server Chart?

  1. Visualizing data trends through line and bar charts.
  2. Creating complex diagrams like fishbone and flow diagrams for presentations.
  3. Generating interactive charts for web applications.

FAQ from MCP Server Chart?

  • What types of charts can be generated?

MCP Server Chart supports area, bar, column, dual axes, fishbone, flow, histogram, line, mind map, network graph, pie, radar, scatter, treemap, and word cloud charts.

  • Is there a cost to use MCP Server Chart?

No, MCP Server Chart is open-source and free to use under the MIT license.

  • How do I install MCP Server Chart?

You can install it via npm using the command: npm install @antv/mcp-server-chart.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago