Chartory is an MCP server published by com.usechartory, hosted at usechartory.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including search_charts, get_chart_spec, get_chart_code, get_tokens.
Chart types, props, JSON Schemas and install commands for the Chartory React chart library.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Find the Chartory chart types that fit a question about the user's data, in plain words ("monthly revenue against target", "where users drop off in signup"). Returns each type's slug, what it answers and its install command.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | How many to return (default 8) |
| query * | string | What the chart should show, in plain words |
| freeOnly | boolean | Only the free types (no licence key needed) |
| question | string | Only types that answer this question |
None yet. Changes appear after a server's second daily check.
Inferred from the host name and headers: what a server runs on, not who runs it.
{
"name": "search_charts",
"title": "Search charts",
"description": "Find the Chartory chart types that fit a question about the user's data, in plain words (\"monthly revenue against target\", \"where users drop off in signup\"). Returns each type's slug, what it answers and its install command.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "How many to return (default 8)"
},
"query": {
"type": "string",
"maxLength": 300,
"description": "What the chart should show, in plain words"
},
"freeOnly": {
"type": "boolean",
"description": "Only the free types (no licence key needed)"
},
"question": {
"enum": [
"Change over time",
"Compare items",
"Part of a whole",
"Distribution",
"Flow between steps",
"Relationship",
"Schedule and status",
"Space and place"
],
"type": "string",
"description": "Only types that answer this question"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}The component, its props, sizes and the JSON Schema of its data prop, for one chart type by slug (from search_charts). Shape the user's data to the schema.
| Parameter | Type | Description |
|---|---|---|
| slug * | string | The type's slug, e.g. waterfall |
{
"name": "get_chart_spec",
"title": "Get a chart's spec",
"description": "The component, its props, sizes and the JSON Schema of its data prop, for one chart type by slug (from search_charts). Shape the user's data to the schema.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"maxLength": 80,
"description": "The type's slug, e.g. waterfall"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}The install command and the component file for one chart type, plus an example file with sample data. Paid types need a Code or Complete licence key sent as the Bearer token.
| Parameter | Type | Description |
|---|---|---|
| slug * | string | The type's slug, e.g. waterfall |
| with | string | chart (default), its widget, or the interactive widget |
{
"name": "get_chart_code",
"title": "Get a chart's code",
"description": "The install command and the component file for one chart type, plus an example file with sample data. Paid types need a Code or Complete licence key sent as the Bearer token.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"maxLength": 80,
"description": "The type's slug, e.g. waterfall"
},
"with": {
"enum": [
"chart",
"widget",
"interactive"
],
"type": "string",
"description": "chart (default), its widget, or the interactive widget"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}Chartory's design tokens (CSS custom properties from chartory.css) in one of the four modes, optionally filtered by a name fragment ("data", "surface", "signal"). Light is :root, dark is .dark; data-theme picks a mode for a subtree.
| Parameter | Type | Description |
|---|---|---|
| mode | string | The mode (default chartory-light) |
| filter | string | Only tokens whose name contains this |
{
"name": "get_tokens",
"title": "Get the theme tokens",
"description": "Chartory's design tokens (CSS custom properties from chartory.css) in one of the four modes, optionally filtered by a name fragment (\"data\", \"surface\", \"signal\"). Light is :root, dark is .dark; data-theme picks a mode for a subtree.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"mode": {
"enum": [
"chartory-light",
"chartory-dark",
"ember",
"ember-light"
],
"type": "string",
"description": "The mode (default chartory-light)"
},
"filter": {
"type": "string",
"maxLength": 40,
"description": "Only tokens whose name contains this"
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}Chartory: 132 chart types for React (shadcn registry) and Figma, in four sizes (xs 311, s 360, m 480, l 800 px wide), in two collections (Hearth, Signal). Types 1 to 100 in Hearth are free and MIT licensed: no key needed (freeOnly: true in search_charts), and no components.json setup: @chartory is in the shadcn registry directory. Flow: search_charts with the question the data answers → get_chart_spec for the props and the data's JSON Schema → get_chart_code (or run the install command) → shape the user's data to the schema. Complete also has six sector packs (@chartory/sector-<ai|saas|fintech|crypto|logistics|e-commerce>: the sector's charts, widgets, dashboard and sample datasets) and their dashboards (@chartory/dashboard-<key>); install them with npx shadcn add. Rules: never scale a chart with CSS, pick the size that fits the card; use the theme tokens (import chartory.css once); a function field such as fmt is passed in code.
Names, descriptions and schemas were written by the server and are shown as data.