Claude

Claude remembers you. It knows nothing about what your company decided last month.

What it changes

An assistant with no company memory starts from zero in every conversation. You re-explain the context, the constraints, what has already been tried. That costs time, and above all it produces errors: it advises without knowing what you already ruled out, and why.

Connected to Verbasil, Claude answers with what the company knows, and cites its sources.

What Verbasil brings to the conversation

Verbasil exposes about twenty read and write tools. In practice, the assistant can:

• retrieve what the company decided, learned, and what is still open;
• search the memory by topic, by person, by period;
• read a contact's context before drafting anything about them;
• propose a write: a settled decision, a learning, a report.

And the rule that makes all of this workable: a write is never applied directly. It arrives in Sources and waits for a human to review it. An assistant writing unchecked into a company's memory would make it useless within a month.

How to connect it

1. Open Verbasil, go to Integrations, AI tools section.
2. Generate an access token, read-only or with write access.
3. In Claude, open settings, then connectors.
4. Add a custom connector with Verbasil's MCP address and your token.
5. Start a conversation and ask Claude what your memory contains.

Claude Desktop and Claude Code use the same connector: one token covers both.

What it does not do

Verbasil fetches nothing FROM Claude: the direction is the opposite. Claude queries the memory; the memory does not go through your conversations.

No write is applied without approval.

FAQ

Does Verbasil read my conversations?

No. Verbasil only ever sees the questions the assistant asks it, never the rest of the exchange.

Can I limit what the assistant is allowed to do?

Yes. A read-only token allows lookups and nothing else.

What happens if I revoke the token?

Access stops immediately. Whatever is already in the memory stays there.