← Registry

Design

usechartory.com

Provides searchable Chartory chart types, component specs, code examples, and design tokens for selecting and implementing data visualizations.

1 endpoint4 known toolsFirst detected November 3, 2026Last detected November 4, 2026

ENDPOINT 1

https://usechartory.com/mcp

No auth detected

MCP server metadata

Name
chartory
Version
1.0.0
Capabilities
tools.listChangedresources.listChanged
Server instructions

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.

Known tools 4

search_charts

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").

Potential side effects
get_chart_spec

The component, its props, sizes and the JSON Schema of its data prop, for one chart type by slug (from search_charts).

Inferred read-only
get_chart_code

The install command and the component file for one chart type, plus an example file with sample data.

Potential side effects
get_tokens

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").

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.chartory]
url = "https://usechartory.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "chartory": {
      "type": "http",
      "url": "https://usechartory.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: chartory
Remote MCP URL: https://usechartory.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "chartory": {
      "url": "https://usechartory.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "chartory": {
      "type": "http",
      "url": "https://usechartory.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "chartory",
  "transport": "streamable-http",
  "url": "https://usechartory.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.