MCPサーバー

chartlink

io.github.oscarleoo/chartlink

このMCPでできること

Creates, styles, publishes, embeds, and automatically refreshes charts and tables from inline data or scheduled external data sources.

check_template_data
Dry run: would this data and these knobs work with the template? Creates nothing
Matches every region value against the template's geography and reports unmatched values with the closest real codes, how many regions would stay grey, and the scale the map would use. No key needed. Use it when unsure of the codes; then create_from_template with the same data and knobs.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['template', 'data'], 'properties': {'data': {'type': 'object', 'required': ['columns', 'rows'], 'properties': {'rows': {'type': 'array', 'items': {'type': 'array', 'items': {'type': ['string', 'number', 'boolean', 'null']}}, 'description': 'Row-major values, one array per row, order matching columns'}, 'columns': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'type'], 'properties': {'id': {'type': 'string', 'minLength': 1, 'description': 'Column identifier referenced by encodings'}, 'type': {'enum': ['string', 'number', 'date', 'boolean'], 'type': 'string', 'description': 'date columns parse ISO-ish strings on their own: "2024", "2024-03", "2024-03-15", "2024-Q2", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.'}, 'label': {'type': 'string', 'description': 'Display label; defaults to id'}, 'dateFormat': {'type': 'string', 'description': 'For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. "%d/%m/%Y" for "15/03/2024", "%b %Y" for "Mar 2024". Removes the day/month guess; ISO-ish strings never need it.'}}, 'additionalProperties': False}, 'minItems': 1}}, 'description': 'The data you intend to send', 'additionalProperties': False}, 'knobs': {'type': 'object', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'template': {'type': 'string', 'description': 'Template id, slug, or page address (sweden/municipalities)'}}}
create_edit_link
Mint a no-login tweak link — hand it to your human
Returns a URL opening the visual tweak panel for ONE chart (text, colors, spacing, label nudges) with no login. PUBLISH FIRST: the editor saves and republishes a published chart, it cannot publish a draft. Scope: view, tweak, and republish that chart only — never delete, never spend credits, nothing else in the workspace. OFFER THIS whenever the human's request is aesthetic fine-tuning: handing over the wheel beats a nudge-by-nudge back-and-forth. The secret is shown once; links don't expire and can be revoked with revoke_edit_link.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'ast_...'}}}
create_from_template
Create a chart from a template with your data and a few knobs — returns an inline preview
The template's design, your data, your words. `knobs` are the template's settings (get_template shows the schema): theme light|dark|editorial, dataType gradient|buckets|categories and surroundings true|false (then waterColor, landColor) for maps, title/description/source/brand {text, fontFamily, fontSize, color}, backgroundColor, and the scale knobs for the dataType (colormap and direction, range, breaks or classes, categoryColors/categoryOrder). data = {columns: [{id, type}], rows: [[…]]}: use the template's column ids, or exactly two columns (region first, value second) for a map. publish: true makes the URLs live in the same call. A success means it validated AND rendered — look at the preview. Region values that match nothing come back as a 400 listing each with its closest real codes, before anything is made — no separate check needed. `config` is the advanced path: the engine's settings, merged after the knobs.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['template', 'data'], 'properties': {'data': {'type': 'object', 'required': ['columns', 'rows'], 'properties': {'rows': {'type': 'array', 'items': {'type': 'array', 'items': {'type': ['string', 'number', 'boolean', 'null']}}, 'description': 'Row-major values, one array per row, order matching columns'}, 'columns': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'type'], 'properties': {'id': {'type': 'string', 'minLength': 1, 'description': 'Column identifier referenced by encodings'}, 'type': {'enum': ['string', 'number', 'date', 'boolean'], 'type': 'string', 'description': 'date columns parse ISO-ish strings on their own: "2024", "2024-03", "2024-03-15", "2024-Q2", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.'}, 'label': {'type': 'string', 'description': 'Display label; defaults to id'}, 'dateFormat': {'type': 'string', 'description': 'For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. "%d/%m/%Y" for "15/03/2024", "%b %Y" for "Mar 2024". Removes the day/month guess; ISO-ish strings never need it.'}}, 'additionalProperties': False}, 'minItems': 1}}, 'description': "Typed columns + row-major rows, shaped like the template's example", 'additionalProperties': False}, 'knobs': {'type': 'object', 'description': "The template's knobs — get_template returns their schema", 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'config': {'type': 'object', 'description': 'ADVANCED: engine settings deep-merged after the knobs', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'publish': {'type': 'boolean', 'description': 'true = published and live in this call; omit while you iterate'}, 'template': {'type': 'string', 'description': 'Template id or slug from list_templates, or the page address (sweden/municipalities, us/texas/counties, london/wards) when you know the place'}}}
get_template
One template's contract: knobs, columns, region codes, an example call
Read this before create_from_template. Returns the template with `contract`: its looks (theme × dataType × surroundings), the knobs JSON Schema, the columns with their roles, the region-code convention with three real codes and a lookup URL, what each dataType expects of the value column, and a complete example call whose shape you copy. Takes an id, the page slug, or the page address as on chartlink.app/maps — sweden/municipalities, us/texas/counties, london/wards — so you can skip list_templates when you know the place.
読み取り専用 冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Template id (ast_…), slug, or page address (place/level)'}}}
list_templates
Templates by need — search, then start a chart from the best match
Templates are named by the NEED they answer (need, asks, tags), each with urls.png (show it to your human) and `columns`: the column ids your data must supply. Pass q with what the person asked for — "map of brazil's states", "ranked bars with flags", "change between two years" — and the list comes back ranked; take the first. Then create_asset with template: <id> and your data — the whole design comes along. Any chart id you were shown works as a template too, not only these.
読み取り専用 冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'q': {'type': 'string', 'description': "What is needed, in the person's words"}, 'tags': {'type': 'string', 'description': 'Comma-separated tags every result must carry, e.g. map,united-states'}, 'type': {'type': 'string', 'description': 'Only this asset type, e.g. "bar"'}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1, 'description': 'At most this many, best first (default 20)'}}}
publish_asset
Publish — snapshot a version and update every embed
Makes the draft live. Returns urls: paste urls.embedIframe on iframe platforms; on Substack insert urls.png as an image and link it to urls.page. Pinned history: urls.png + '?v=N'.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id'], 'properties': {'id': {'type': 'string'}, 'note': {'type': 'string'}, 'premium': {'type': 'boolean', 'description': 'Spend one paid credit to publish as premium (2400px, SVG, your branding, no badge) in this call'}}}
signup
Get an API key — no account, one call
Creates a workspace and returns its API key (shown ONCE — keep it). Works on a keyless connection; every other tool needs the key. Then put the key where your client keeps it (plugin api_key setting, the Authorization header, or CHARTLINK_API_KEY for the npx bridge) and reconnect.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'ref': {'type': 'string', 'description': 'Where you heard of chartlink — free text'}, 'name': {'type': 'string', 'description': 'A name for the workspace (the project, the newsletter…)'}}}
submit_feedback
Report a gap — don't silently give up
If a capability is missing, a schema fights you, or docs are wrong: record it here so the owner can fix it. One report per distinct issue, with a real description — reports get fixed same-day when they say what you tried, what you expected, and what happened (title-only reports can't be acted on).
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['type', 'title', 'description'], 'properties': {'type': {'enum': ['bug', 'feature_request', 'limitation', 'documentation_gap', 'other'], 'type': 'string'}, 'title': {'type': 'string'}, 'assetId': {'type': 'string'}, 'description': {'type': 'string', 'minLength': 40, 'description': 'What you tried, what you expected, what happened instead — include the asset id if one is involved'}}}
update_asset
Update a draft (deep-merge patch, or replace the config) — returns an inline preview image
configPatch is DEEP-MERGED: objects merge recursively, arrays replace wholesale, null clears a key — send only what changes. To REMOVE keys (drop document.aspect, delete one of texts[]) pass `config` instead: it REPLACES the whole config (get_asset returns the current one to edit). `data` (if given) replaces rows wholesale. Requires expectedVersion from the last envelope; on 409 re-merge onto the returned `current`. Updating does NOT publish by default — pass publish: true to publish in the same call, or call publish_asset separately.
破壊的操作あり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['id', 'expectedVersion'], 'properties': {'id': {'type': 'string'}, 'data': {'type': 'object', 'required': ['columns', 'rows'], 'properties': {'rows': {'type': 'array', 'items': {'type': 'array', 'items': {'type': ['string', 'number', 'boolean', 'null']}}, 'description': 'Row-major values, one array per row, order matching columns'}, 'columns': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'type'], 'properties': {'id': {'type': 'string', 'minLength': 1, 'description': 'Column identifier referenced by encodings'}, 'type': {'enum': ['string', 'number', 'date', 'boolean'], 'type': 'string', 'description': 'date columns parse ISO-ish strings on their own: "2024", "2024-03", "2024-03-15", "2024-Q2", full ISO timestamps, or epoch numbers. Anything else needs dateFormat.'}, 'label': {'type': 'string', 'description': 'Display label; defaults to id'}, 'dateFormat': {'type': 'string', 'description': 'For date columns whose strings are NOT ISO-ish: a strftime-style parse hint tried first — tokens %Y %m %d %b %B %q %H %M %S, e.g. "%d/%m/%Y" for "15/03/2024", "%b %Y" for "Mar 2024". Removes the day/month guess; ISO-ish strings never need it.'}}, 'additionalProperties': False}, 'minItems': 1}}, 'description': 'Typed columns + row-major rows. A date column whose strings are not ISO-ish takes dateFormat (e.g. "%d/%m/%Y").', 'additionalProperties': False}, 'brand': {'type': ['string', 'null']}, 'title': {'type': 'string'}, 'config': {'type': 'object', 'description': 'REPLACES the whole config — the way to remove keys; applied before configPatch if both are given', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'publish': {'type': 'boolean', 'description': 'true = publish immediately after this update succeeds (one call instead of two)'}, 'showcase': {'type': 'boolean', 'description': 'Offer this chart as a template in the public gallery and list_templates (once published). Workspace keys only.'}, 'configPatch': {'type': 'object', 'description': 'Deep-merged onto the current config', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'expectedVersion': {'type': 'integer', 'maximum': 9007199254740991, 'minimum': 1}}}
whoami
Verify your API key
Returns key name + workspace. Call this first — non-destructive auth check. Everything you write is stamped createdBy/updatedBy = key name.
読み取り専用 冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
変更
update_asset
2026年10月1日2:48
変更
create_from_template
2026年10月1日2:48
変更
check_template_data
2026年10月1日2:48
変更
create_from_template
2026年9月25日2:55
変更
check_template_data
2026年9月25日2:55
変更
get_template
2026年9月25日2:55
削除
upgrade_to_premium
2026年9月23日2:47
削除
update_brand
2026年9月23日2:47
削除
unpublish_asset
2026年9月23日2:47
削除
set_data_source
2026年9月23日2:47
削除
revoke_edit_link
2026年9月23日2:47
削除
replace_asset_data
2026年9月23日2:47
削除
list_geographies
2026年9月23日2:47
削除
list_brands
2026年9月23日2:47
削除
list_asset_types
2026年9月23日2:47
削除
list_assets
2026年9月23日2:47
削除
get_spec_schema
2026年9月23日2:47
削除
get_billing
2026年9月23日2:47
削除
get_asset
2026年9月23日2:47
削除
fetch_data_source
2026年9月23日2:47
削除
duplicate_asset
2026年9月23日2:47
削除
delete_asset
2026年9月23日2:47
削除
create_checkout_link
2026年9月23日2:47
削除
create_brand
2026年9月23日2:47
削除
create_asset
2026年9月23日2:47
削除
clear_data_source
2026年9月23日2:47
追加
create_from_template
2026年9月23日2:47
追加
check_template_data
2026年9月23日2:47
追加
get_template
2026年9月23日2:47
変更
list_templates
2026年9月23日2:47