Ailimu

Query your FileMaker data in plain language, from an AI agent.

Ailimu is a small server you run yourself. Point it at a FileMaker file, decide what an AI agent may see, and publish. The agent receives a set of tools shaped around the questions people ask, such as retrieving a record, searching a date range, or running a script you have chosen to expose, and answers from your live data.

The problem

A FileMaker solution is usually the most complete record a business holds of itself, and among the hardest to interrogate. The answer to a question such as "which customers have invoices unpaid beyond sixty days, and what are those invoices attached to" is present in the data, but retrieving it means opening the correct layout, constructing a find, exporting the result and joining it to something else by hand. The question therefore goes to whoever knows the solution best, or it is not asked at all.

Providing an AI agent with a raw connection does not resolve this. An agent given a complete schema and a query language has to infer too much: which of several hundred table occurrences holds the live records, what the zz_ and zg_ calculation and global fields are for, and whether an empty column is empty because there is no data or because it was never adopted.

Ailimu resolves those questions during setup, under your review:

It reads the real schema rather than a layout's view of it: true field types, declared keys, relationships, row counts, and the field comments already written in your solution.
It determines what each table is for, whether core records, transactions, lookups, logs or join tables, and states its reasoning so you can correct it.
It samples a bounded number of rows to identify columns that are never populated, and text fields holding only a handful of distinct values, so that search parameters carry meaning.
You decide, field by field, what may be read, what may be searched, and what, if anything, may be changed.

The agent is left with a compact set of well described tools rather than a database it must reverse engineer. That is the entire premise: an agent given twenty good tools answers more reliably than one given two hundred bare ones.

What leaves your network

This is the first question any competent reviewer asks, so here is the direct answer.

Ailimu runs on your infrastructure. It is not a cloud service, it does not sync, and there is no copy of your database anywhere but your own server. But when the agent answers a question about your data, it has to see that data. The rows a tool returns are sent to the model, in that moment, to be reasoned about. This holds for every connector of this kind, including those offered by Claris and Ottomatic. Any product claiming otherwise is describing something that cannot answer questions.

Never leaves your network	Goes to the model when a tool is called
Your FileMaker account name and password. Read from the environment, never written to the config file, never handled by the browser.	The rows that the specific tool returned: the fields you marked readable, for the records that matched.
Any table or field you did not expose. It is not in the tool schema, so it cannot be asked for.	The names and descriptions of the tools themselves, so the agent knows what it may ask for.
Your database as a whole. Nothing is copied, exported, mirrored or indexed. Every tool call reads FileMaker live.
Sampled values from setup. They are summarised into counts and shown to you, then discarded. They are never written to the config or the schema cache.

Controls you have:

Read-only is on by default. While it is on, no update tool and no script tool is generated at all, irrespective of what else is selected.
Exposure is per field. Read means the value can come back; search means it can be filtered on. Everything else is invisible.
Your FileMaker privilege set still applies. Ailimu connects as an account you create. Anything that account cannot see stays unseeable, whatever the config says. Issue it a restricted account.
Everything is audited. Writes and script calls are always logged, because nothing else records what a script did.
Container fields are never sent. They are excluded from every tool.

If your data may not reach a third-party model at all, then no connector of this kind is appropriate. That is a decision about the model, not about Ailimu.

How it fits together

  Your network                                    Anthropic
  ┌───────────────────────────────┐
  │  FileMaker Server             │
  │        ▲                      │
  │        │ OData / Data API     │
  │        │ (your account)       │
  │  ┌─────┴──────┐               │        ┌──────────────┐
  │  │  Ailimu    │◀──────────────┼────────│  Claude      │
  │  │  connector │   MCP over    │  tool  │              │
  │  └────────────┘   HTTPS       │  calls └──────────────┘
  └───────────────────────────────┘

Ailimu speaks MCP, the open standard for giving an agent tools. Claude connects to it the same way as to any other MCP server.

What it is not

Not a chat interface. You bring the agent; Ailimu supplies the tools.
Not a reporting tool. It answers questions live; it does not build dashboards.
Not a sync engine. No copy of your data is made.
Not a replacement for your privilege sets. It is another client, subject to them.

Where to go next

Start with Install. A first run takes about ten minutes: pull the image, set two environment variables, open the wizard, tick the tables you care about, publish, and paste one command into Claude.