Open interface

Our tools in your assistant

The logistics glossary, the site search and the free freight calculators stand ready as an MCP server. Anyone using Claude, ChatGPT or an agent of their own connects to it — and asks us from there, without switching windows.

https://www.logcons.at/api/mcp.php

Why at all

Every connection its own project — that does not scale

Until now the rule was: every system needs its own adapter. TMS, ERP, freight exchange, customs data — every connection a project with a quote, a deadline and an acceptance test. With two systems that works. With twelve it is the reason why nothing talks to anything else.

One plug instead of a hundred cables

MCP — Model Context Protocol — is for AI what USB was for devices: a standard both sides speak. Whoever offers something describes once what it can do; every assistant that knows the protocol calls it. Nobody builds the connection between exactly these two houses any more.

Not guessing, but looking it up

A model without a connection answers from its training knowledge — it knows what stood in texts, not what applies today. With a tool alongside it looks things up: it makes a call, gets an answer and carries on calculating with it. The difference is not in the phrasing but in whether the figure is right.

Sounding right or calculating

An AI that does not know which load is where, what a carrier costs and which framework agreement applies can only sound plausible. In transport planning that is worthless: a plausible proposal nobody can recalculate costs more time than none at all.

And how much of that runs here? This server provides the public tools of this portal — the logistics glossary, the site search, the free calculators. It knows no login and no operational data; whoever calls it gets the same as everybody else. That is on purpose and not a building site. What expressly does not go out is further down: What does not go out – read on →

The content

The three tools

What goes out here stands publicly on this website anyway. The difference is that your assistant can now look it up itself instead of referring you to a page.

logistik_begriff

Looks a term up in the logistics glossary — from advice note through cabotage to customs seal. Delivers the explanation, not just a reference.

seite_finden

Finds the page for a keyword: empty-run rate, CO₂e methodology, tender. For the case where the answer is longer than a paragraph.

rechner_finden

Names the matching free calculator for a computational question, along with its address. It does not calculate itself — it shows where the calculation rule is set out.

In three minutes

Connect

The server requires no registration and no key. There are two routes; which one works depends on your program and its version — the vendors' interfaces change faster than this page can keep up.

Route 1: as your own connector

In Claude (desktop or web) under Settings → Connectors → Custom Connector enter the address:

https://www.logcons.at/api/mcp.php

Other programs call the same thing “Remote MCP Server” or “HTTP server”. All that is ever asked for is this one address.

Route 2: via a bridge

If your program only accepts local servers, this is translated by mcp-remote. In the configuration file:

{ "mcpServers": { "logcons": { "command": "npx", "args": ["-y", "mcp-remote", "https://www.logcons.at/api/mcp.php"] } } }

You can tell whether it worked by your assistant listing the three tools above. Ask as a test: “What does loading metre mean?” — the answer should come from the logistics glossary and not from the model's memory.

The limit

What does not go out

An MCP server is a door a foreign agent reaches through. What lies behind it is decided beforehand — not with the first user.

Not reachable

  • Orders, shipments, trip data
  • Customer and carrier master data
  • Prices, revenues, contribution margins
  • Fleet and driver data

The file behind this interface does not even load the corresponding tools. This is not a permissions concept somebody could reconfigure — the code is not there. A test holds this limit in place so that it stays one.

What we see

Your requests run through our server, so technically we see them. We do not evaluate them and do not pass them on. For the rate brake, your IP address is stored salted and hashed — not the address itself, and not for longer than a minute.

There is no language model behind this interface. What you ask goes to no AI provider, to no third country and into no training.

For IT

Technical details

Protocol

JSON-RPC 2.0 over HTTP POST, “streamable HTTP” without an event stream. A GET is answered with 405 — as it should be when no SSE is offered. Supported: initialize, tools/list, tools/call, ping.

Increment

60 calls per minute and sender. Above that the server answers with 429 and a Retry-After. That brakes loops, not people.

Findability

A machine-readable pointer lies at /.well-known/mcp.json. There is no generally binding convention for this — the reliable route remains entering the address by hand.

If something does not work, write to us with the version of your program and the error message. An interface that only works with us is not one.

Direct Inquiry

You need more than the three tools?

For customers we open the same technology onto their own data — with a login, a log and a contract covering who may see what.