For AI builders

Ilu Rennik holds one person's confirmed facts about their life, each with the document or words behind it. Their accounts, insurance policies, IDs and documents and where they are kept, the people who act for them, addresses, membership and policy numbers, and the dates things renew or fall due.

It reads the documents they add and puts what it finds in front of them as potential facts. Nothing is kept until they say yes. It never reads their mail. The same search reaches every file they added, so an answer that is not on file yet can still be found.

A person connects Ilu Rennik to the AI they already use. This page is for that AI, and for the people who build it. It describes every tool, every input, and how a good session goes.

Connect

Ilu Rennik is a remote MCP server over streamable HTTP. There are two addresses. The person decides which one an AI gets.

claude mcp add --transport http ilu-rennik https://mcp.ilurennik.com/v1/owner/mcp

https://mcp.ilurennik.com/v1/owner/mcp

https://mcp.ilurennik.com/v1/owner/mcp

https://mcp.ilurennik.com/v1/owner/mcp

code --add-mcp '{"name":"ilu-rennik","type":"http","url":"https://mcp.ilurennik.com/v1/owner/mcp"}'

https://mcp.ilurennik.com/v1/agent/mcp

Sign in and security

• Sign in is OAuth 2.1 with PKCE (S256) and dynamic client registration. No key or token is ever pasted.
• The person signs in on Ilu Rennik's own screen and chooses how long the connection lasts. It is 90 days unless they choose otherwise, and never more than a year.
• A call with no token, or a token that has ended, gets a 401 that names where to sign in. Many refused tokens in a short time are slowed with a 429.
• The person sees every connected app in Settings, when it connected and when it last read, and can end it there. It stops at once.

A first question

Once connected, these words start the first conversation. They work with no plugin and no setup.

The Ilu plugin

The Ilu plugin puts the connection and a short guide to the first conversation in one install, for Claude and for ChatGPT. The guide takes a person's AI through what is on file, a few finds at a time, each kept only on their yes.

The plugin is not in Claude's or ChatGPT's directories yet. Until it is, connect the address above, then say Get started with Ilu. It works the same without the plugin.

What a person's Ilu holds

Ilu Rennik holds one person's confirmed facts about their life, each with its source and when it was confirmed, such as insurance policies, bank and retirement accounts, IDs and where documents are kept, the people who act for them, addresses, membership and policy numbers, and renewal and due dates. It also searches the documents they gave it. Every fact here was confirmed by the person and shows where it came from, unlike what an assistant remembers from past chats.

• Facts. One statement each, with its receipts (the document or words it came from) and when it was last confirmed. A fact replaced by a newer one keeps its history.
• Shelves. Facts sit on shelves, named as on the person's screen. Money, Insurance, Home and cars, Health, Documents, Accounts, Business, Estate, People, Preferences, Travel and events, and Your vault. A person can also make shelves of their own.
• Potential facts. What was found but not yet kept. Each waits for the person's yes.
• Documents. Files they added, searchable by their text.
• People. The people they name, such as their lawyer or accountant, with firm, role and how to reach them.
• Seats. People the person has let see named shelves.
• Sealed facts. Named, with their contents never returned to any AI.

When to look

Its tools fit questions about those things, and tasks that depend on them, such as booking travel, paying or renewing something, filling in a form or contacting a provider. find looks up one thing, get_record reads a shelf, and open with look_for answers what a document says. where_things_stand says what is on file and what to offer next.

The first session

where_things_stand returns stage (new, waiting or settled) and next, the one offer to make now, chosen from what is on file, with suggested words for the AI to put in its own. The same two ride every tool's result while the account is new or something waits. The offers, in the order they come.

1. Someone new. "Ilu Rennik is connected. Now when something about your life matters, like a policy number, a renewal date or who your doctor is, I can look it up there instead of guessing, and so can any other AI you connect. You decide what goes in, and I can help fill it. Want to start by dropping in a document, or just tell me something, like who insures your car?"
2. What is waiting. "4 things are still waiting from last time. Want to go through them?"
3. What is missing. "You have Cigna on file but no policy. Want to add it?"
4. Who else should see it. "Should anyone else see some of this, like your accountant?"

An offer they turn down is never made again; the AI says so with declined. One left unanswered comes back in a later conversation, up to three. After the first conversation there is one offer a conversation. Nothing is kept without their yes.

Answering from documents

A question about what a document says, such as a deductible, what a policy covers or whether a claim is paid, takes two calls. find locates the document, and open with look_for returns only the passages that answer, in any language. Never page through a long document part by part. For a health question, find the policy first, then its terms.

{
  "name": "find",
  "arguments": {
    "query": "car insurance deductible",
    "about": "Qualitas"
  }
}

// Example values
{
  "total": 3,
  "by_kind": { "fact": 1, "document": 2 },
  "shown": 3,
  "items": [
    { "id": "fact:8c1e40d2", "kind": "fact", "date": "2026-03-02",
      "title": "Car insurance, Qualitas",
      "why": "Policy 7741-20, 2022 Honda CR-V, renews 2 March" },
    { "id": "doc:51f0a9b7", "kind": "document", "date": "2026-03-02",
      "title": "poliza-2026.pdf", "matched": "meaning" }
  ],
  "next_cursor": "eyJvIjp7ImRvY3VtZW50IjozfX0"
}

{
  "name": "open",
  "arguments": {
    "id": "doc:51f0a9b7",
    "look_for": "what is my deductible"
  }
}

// Example values
{
  "looked_for": "what is my deductible",
  "passages": [
    { "text": "Daños materiales. Deducible 5% del valor comercial...",
      "part": 2, "offset": 8120 }
  ],
  "matched_by": "meaning and words",
  "passages_in_document": 212
}

The first time a long document is asked about, it may answer by words only and say it is being read by meaning. Ask again a minute later for the fuller answer.

Keeping and proposing

Nothing is kept without the person's yes. keep records their yes as the receipt, and propose puts a find in front of them to decide later.

A document sent with propose as one thing has its name as subject and each value in details, up to 40, so they keep all of it with one tap.

Seats

A seat lets someone the person names, such as a spouse, an accountant or an executor, see named shelves. Before giving or changing a seat, list the shelves, their own included, with what is on each, and let them choose. Every seat change happens on their word, with owner_said.

Ids

find returns ids with a prefix that says what each one is. Pass them to open, up to five at once.

Long answers

• Every tool takes part. When an answer is long, it ends with next_part. Pass that number to read on.
• find returns next_cursor while more matches remain. Pass it back as cursor. total is the true count, not the page size.
• open on a document returns next_offset. Pass it as offset. Prefer look_for.

Limits and errors

Privacy

Sealed facts, passwords, full account numbers and full ID numbers are never returned. Every call is on a log they can read.

Their data is not sold and not used to train AI. The full account of what is read, where it lives and who touches it is on the Privacy page.

Tools

All 14 tools on the owner address, with every input. Every tool also takes part.

Start here

Look things up

People

Keep and change

Shelves and seats

Files and connections