Connect your own AI to your Druma data

The trucks that will be empty in Poland on Thursday, and the drivers on them, sit on three screens in Druma: the truck list, the plan and the drivers. An AI client connected to your Druma data reads all three and answers in one reply.

You can connect one in two ways. Your own AI client connects over MCP, a connection Druma has tested end to end with Claude. Druma AI is a chat screen inside Druma that runs on an API key from your own AI provider.

A question, a proposal, one click

On Wednesday afternoon a planner asks Claude for exactly that. Claude answers with three trucks, the last unloading point of each and the driver. The planner then asks it to put a Poznań to Lyon load on one of them.

Claude can only propose that. Druma shows the proposal as a plain summary and changes nothing until the same planner confirms it. A proposal nobody confirms expires after ten minutes, and the truck stays where it was.

The question, and whatever the AI read to answer it, go to the AI provider you chose.

Your own AI client over MCP

MCP, the Model Context Protocol, is an open standard that AI clients use to connect to data sources. Druma runs an MCP server your client connects to.

Claude on the web, desktop or phone connects through a sign-in. The planner logs in to Druma on a consent screen that names the client and the permissions it asks for, and picks the company if they work for more than one. Other standard MCP clients, such as ChatGPT, connect the same way; in ChatGPT the connector is added in developer mode. Developer tools such as Cursor or Codex CLI use a personal access token instead, created in Settings. Druma shows the token once. It is valid for 90 days by default and can be revoked at any time.

Every call runs as the signed-in user, with that user's role and company. The AI cannot run its own database queries, delete anything or change records in bulk. Each call is written to an audit log, and a user gets 60 calls a minute.

A connection reads by default. It can propose one change, a truck assignment, and only when the connection was granted the planning permission at sign-in and the user's role may assign trucks in Druma.

Druma asks no data-sharing consent for an MCP client, but an administrator ticks a box under Connected AI in Settings to confirm that your company takes responsibility for the AI apps it connects. What the app sends to its provider is your decision.

Druma AI, the in-app assistant

Druma AI answers questions about your data and can prepare four kinds of change: assign a truck, notify a client, add a billable line to an order, move a stop. Each one appears as a card with Approve and Reject. The model cannot apply anything itself, and it works with the permissions of the user it is talking to.

It runs on your own key from Anthropic, OpenAI or Google Gemini. The key is stored encrypted and never sent back to the browser. Before the key is saved, a company administrator ticks a data-sharing notice and Druma records that consent. From then on, questions and the data they pull go to that provider, which may process them outside the EU under its own terms.

Who pays

Your AI provider bills you directly, by the amount of text processed, counted in tokens. A long question about a full month's plan costs more than a short one about tomorrow. Druma charges nothing for the connection.