Quickstart

1. Connect your agent

In Claude Code, one command:

claude mcp add --transport http indraft https://api.indraft.io/mcp

That sends you through your browser to authorize it. Nothing is pasted, and you can revoke the connection later from the workspace.

In the Claude apps, ChatGPT, or any other MCP client, add the same endpoint in the client's own connector settings:

https://api.indraft.io/mcp

For something that runs without a person present, a CI job or a server, use a token from Settings instead of the browser flow. Connecting Claude has that form and the .mcp.json a repository shares.

2. Give it this

Set up Indraft for my business. Read its CRM schema first, then tell me what you think we do and how you plan to model it, and wait for my answer before you write anything. Configure the pipeline to match how we actually sell, add the custom fields that earn their place, and if something we run on is not a company, contact, opportunity, interaction or task, define an object type for it rather than forcing it into a field. Then populate what you already know from our conversations. Do not create duplicate people or companies: if an upsert comes back ambiguous, tell me rather than picking one.

This prompt ships with the product and is versioned in the repository rather than written into this page, so what you copy here is what the product tests against.

3. Watch it work

The activity view fills as the agent writes. Every change carries the actor that made it, whether it was observed or inferred, and which surface it came through, so you can tell an agent's claim from a colleague's correction at a glance.

What a first session costs

Nothing, and nothing stops halfway. Every new workspace runs on Scale limits for 7 days, so an agent can configure the pipeline, add the fields it needs, and populate months of history without meeting a number. No card.

After that you fall back to the plan you are on. Free holds 25,000 records and 10,000 changes a month, comfortably more than a founder-operator with a couple of dozen customers needs for the backfill and then some.

What happens if you go over depends on whether you are paying. On a PAID plan nothing stops: records and changes past your allowance are billed at your plan's rate, and your total never exceeds the price of the cheapest plan that covers the month. On FREE, writes are refused and nothing else changes, because there is no subscription to bill them to: everything stays readable, correctable, and exportable, and archiving what you are not working brings you back under without deleting anything.

There is no capability behind a paywall: merge, undo, provenance, bulk writes, webhooks, export, and MCP are on every plan, because those are what the product is. Paid plans raise the numbers.

One limit that is per call rather than per month: a bulk request carries at most 100 operations. A population run makes several of them.

If something is refused

Read the recoveryHint. Every failure carries one, written for an agent rather than for a human reading a log, and it says what to do rather than what went wrong. An ambiguous upsert, for example, returns candidates and writes nothing: Indraft does not guess which of two people you meant.