Flourish

Create and edit Flourish data visualisations.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Flourish connector does

The Flourish MCP server connects Flourish — the Canva-owned data-visualisation and storytelling platform — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 10 tools that read templates, create charts from your data, and rewrite an existing chart's data and settings. Sign-in is OAuth with two scopes. Publishing stays with you.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Flourish tools (10)

  • flourish_list_templates
  • flourish_list_visualisations
  • flourish_get_template_details
  • flourish_get_visualisation_data
  • flourish_get_visualisation_settings
  • flourish_create_visualisation
  • flourish_duplicate_visualisation
  • flourish_update_visualisation_data_bindings
  • flourish_update_visualisation_data
  • flourish_update_visualisation_settings

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The connector cannot publish, and that is the design. Nothing here reaches a public URL, an embed code or a downloadable HTML bundle. If you want the chart live, you open the editor. This is a limit and a safeguard at once.
  • No version history and no undo. Flourish states plainly that MCP edits to an existing project have neither, and calls it a beta-phase item it is monitoring. flourish_duplicate_visualisation is the only recovery mechanism, and only if you use it first.
  • Flourish publishes no tool list for this server. The 10 names come from Anthropic's directory. We could not diff them against a vendor enumeration of names because none exists — but Flourish's published statement about what the connector *cannot* do is a stronger constraint than a name list, and the advertised OAuth scopes independently agree with it.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here.
  • Data reshaping can silently corrupt values. Flourish warns that when the agent reformats data — long to wide, for example — it "can occasionally produce incorrect values, especially with large or complex datasets", and asks you to double-check. This is the failure mode to watch, because a wrong chart looks exactly like a right one.
  • The agent cannot fix a column type. Flourish states that if the agent infers a column's type incorrectly, treating dates as text for instance, it cannot correct that programmatically. You must change the data type in the Flourish editor.
  • The agent cannot change your theme. Flourish states a default theme is applied to newly created visualisations as in the editor, but the MCP "can't change or switch themes".
  • Direct uploads cap at 1,000 rows or 1MB. Larger datasets need another route; Flourish says the agent will guide you to alternatives.
  • AI features are off by default on company accounts and need both an admin action and a per-user one before the connector works at all.
  • Connections are per user. No shared team connection exists.
  • A published chart can carry its data to strangers — but only once a person publishes it. Flourish's publishing flow offers data download links, and on Free accounts published projects are duplicable by default, copying the project and its data. Relevant when *you* publish what the agent built, not when the agent builds it.
  • The directory's documentation URL redirects. Anthropic lists .../16487012057999-Flourish-MCP-connector-an-intro; the article's canonical slug is .../16487012057999-Flourish-Connector-an-intro. Same article, renamed. The help centre's Cloudflare layer returns 403 to plain clients, so we read it through Zendesk's public help_center article API on the same host.

Frequently asked questions

Can the Flourish connector publish a visualisation to a public URL?

No. Flourish states on its Connector product page that publishing still happens in the Flourish editor so you can review the visualisation before it goes live. No tool among the ten carries a publish, share or embed verb, and the server advertises only visualisation read and write scopes. The agent returns an edit link, and a person clicks Export and publish.

What OAuth scopes does the Flourish MCP server request?

Exactly two, and they are real application scopes. The server's RFC 9728 descriptor advertised visualisation:read and visualisation:write on 2026-08-23, and its authorization server metadata advertises the same pair. The boundary falls between reading a chart and changing one, which is the useful place. It does not separate creating a new chart from overwriting an existing one.

Does the Flourish connector expose the data behind my charts?

Yes, in both directions. flourish_get_visualisation_data reads the dataset out of an existing visualisation into the agent's context, and flourish_update_visualisation_data writes a dataset in. Flourish confirms your AI tool processes the data you provide. Nothing becomes public, because a chart stays private until a person publishes it in the editor.

Can the connector overwrite or delete an existing Flourish chart?

It cannot delete one, and it can overwrite one. No tool carries a delete, remove or archive verb, and Flourish's project-deletion flow has no counterpart in the listing. But three update tools rewrite an existing visualisation's data, data bindings and settings, and Flourish states there is no version history or undo for connector edits.

Why does the Flourish connector say MCP is not enabled for my company?

Because AI features are off by default on Flourish company accounts. Flourish states this is intentional and does not depend on which paid plan you are on. Your company admin must click Enable Connector in company settings, and your individual account needs the feature enabled too. Personal accounts enable AI-powered features in account settings.

Does the Flourish connector use my Flourish AI credits?

No. Flourish states that for the Connector, token cost sits entirely with your chosen AI tool rather than with Flourish, and that the Connector does not consume Flourish Assistant credits. The AI processing happens in Claude or ChatGPT, so usage is billed through that tool. The Connector is available to all Flourish users.

How large a dataset can the Flourish connector handle?

Up to 1,000 rows or 1MB when you upload data directly, per Flourish's help documentation, with the agent guiding you to alternatives above that. Because MCP is an open protocol, your AI tool can also pull data from other connected sources such as Google Sheets, databases or APIs and pass it straight into Flourish.

Can two people share one Flourish MCP connection?

No. Flourish states the MCP is authenticated on a single user level, so each team member connects their own account. The connector then respects your existing Flourish permissions: if you have edit access to a visualisation the agent can change it, and if you do not, it cannot. Charts inherit the editor's access controls.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Flourish to work.

Connect Flourish once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.