Plantactic in Claude

You can now connect Plantactic to Claude, hand it a set of contracts, and ask what happened to ARR.

Not a chatbot guessing at a spreadsheet. The numbers come from the same calculation engine the product runs, so what Claude tells you and what your dashboard shows cannot drift apart.

What it looks like

You: Upload these contracts and tell me what happened to ARR through 2026.

Claude: Closing ARR reaches $3.7M by December 2026, up from $948K twelve months earlier. The step in April is two enterprise contracts starting in the same month.

You: Give me that as a PDF for the board pack.

Claude: Ready — 56 pages, every metric across 60 periods.

In between, Claude created a dataset, uploaded the rows, computed the full grid — ARR, MRR, CARR, CMRR, TCV, ACV, bookings, logo counts and the growth rates over them — and rendered the report.

Charts, without asking for them

Every metric comes back with its formatting metadata: whether a number is currency, a percentage or a count, and to what precision. That existed so a partner's own client could render our API correctly. It turns out to be exactly what a model needs to draw an axis properly rather than guess.

So "chart the ARR waterfall" works, and the units are right.

Connecting

In Claude, Settings → Connectors → Add custom connector, and use:

https://mcp.plantactic.com/mcp

Leave the OAuth fields empty — the server registers Claude itself. You'll sign in to Plantactic, see what you're approving and where it returns you, and you're connected.

You don't need an API account first. If you have a Plantactic login but have never touched the API, one is created and linked when you approve.

What it will and won't do without asking

Reading doesn't interrupt you: listing datasets and computing metrics just run.

Uploading contracts always asks first. A new version becomes the active one and supersedes what was there, so every later answer about that dataset changes — that isn't something to do quietly.

What the connector can see

It's a translation layer, and it holds nothing of yours.

It never receives your password. It doesn't see your conversation beyond the arguments of the call it's asked to make, and it has no access to Claude's memory, your chat history, or your files. Every request it makes carries your token rather than a credential of its own, so it reaches exactly what you can reach. Disconnect and that token stops working on the very next request.

A connected account always runs in live mode — the credential the consent flow creates is issued live, and there's no sandbox variant of a connected session. Test mode applies to API keys used directly over HTTP. So if you'd rather not start on data you rely on, point it at a dataset you create for the purpose: nothing you upload changes an existing one.

Where to read more

The connector guide covers the tools, the shape of a contract row, and the permission model. Our privacy policy has a section specific to the API and the connector — what we store, what we don't, and how long exports live.