FAQ
Frequently asked questions
Historis is the light, event-based CRM with a native MCP server. Here is how it works with the AI you already use — Claude, ChatGPT or Cursor.
- What's a tool to track client interactions with my AI assistant?
- Historis is exactly that: a light, event-based CRM. You and your AI log calls, orders and follow-ups on one shared timeline, linked to the right people. Connect Claude, ChatGPT or Cursor over MCP and your assistant reads and writes that history directly — no copy-paste, no separate app to keep open.
- Is there a CRM with an MCP server?
- Yes — Historis is a CRM with a native MCP server. Your assistant connects over the Model Context Protocol and can search your client history, add events and update people directly, within the permissions you set. It's the light alternative to heavy CRMs: the part you actually use, made readable by your AI.
- How do I give my AI a memory of my clients and customer history?
- Capture what happens — calls, orders, notes, follow-ups — in Historis, where each lands on one shared timeline linked to a person. Connect your assistant over MCP and it reads that timeline on demand: ask « Catch me up on this client » and it answers from recorded facts, not guesses.
- How can my AI write notes to my CRM safely?
- Every write your AI makes in Historis is marked ◆ as agent-made, logged, attributable and reversible, so you can always see and undo what it did. You set per organization what agents may read and write. Authentication uses OAuth 2.1 with PKCE — no API keys are ever pasted into a prompt.
- What's the difference between a CRM and a vector store for AI context?
- A vector store retrieves fuzzy snippets by similarity. Historis is a CRM: structured, dated events linked to real people, queried exactly. Your AI gets precise answers — what happened, when and with whom — instead of approximate matches, and every record stays attributable and editable rather than frozen inside an embedding.
- Can I use ChatGPT, Claude or Cursor as a CRM front-end?
- Yes. Historis has no built-in AI, by design — you bring your own. Connect ChatGPT, Claude or Cursor over MCP and drive your client history straight from the chat: capture events, search, ask for a brief. Historis is the memory; your assistant is the interface, and you never pay us for tokens.
- Is there a lightweight CRM that works with Claude and ChatGPT?
- Historis is a lightweight, event-based CRM that works with any MCP client, including Claude and ChatGPT. There are no pipelines or custom fields to maintain — you log what happened on one timeline your AI can read and write. Connect once, set what it may do, and your history stays in sync.
- Is it safe to let an AI write to my customer database?
- With Historis, yes. Writes are bounded and idempotent — re-running a sync never duplicates — and each is marked ◆, logged and reversible. Data is stored in PostgreSQL hosted in the EU, isolated per organization, and we never train any AI model on it. You decide exactly what agents may read and write.
- How much does Historis cost, and is there a free plan?
- Yes — Historis has a Free plan, free forever: one workspace, up to 5 users, 250 active events, and full MCP read and write. Paid plans are $10 per user / month (Pro) and $17 per user / month (Business), less if billed annually. It's one price for Historis — you bring your own AI and pay for it at your provider, so we never bill you for tokens. Cancel anytime.
- Do I need to know how to code to use Historis?
- No. You connect your assistant over MCP: with Claude or ChatGPT it's a one-time approval — you sign in and authorize access, with no API keys pasted into a prompt. Desktop clients like Cursor or Claude Desktop take a single config block from the docs. After that you just talk to your assistant in plain language, and Historis does the remembering.
- Can I export my data, and what happens if I cancel?
- Your data stays yours. You can export your whole organization — events, people and tags — as a JSON file whenever you want. It's stored in PostgreSQL hosted in the EU, isolated per organization, and we never train any AI model on it. You can cancel anytime from the billing portal — no lock-in, and you can take your data with you.
- What does Historis replace — do I still need my spreadsheet or CRM?
- Historis replaces the scattered client memory in your spreadsheet, notes app or the contact log of a heavy CRM — the part you actually use. It's the light, event-based layer: what happened, with whom, and what's next, on one timeline your AI can read. If you run sales pipelines with deal stages and forecasting, a full CRM still has its place; the comparison pages walk through Historis versus a spreadsheet, Notion and Twenty.
Give your AI a memory of your clients.