- Home
- Open protocols
- MCP Server
MCP Server
Find ferry routes and sailings, check live capacity and work with bookings — BORA's operations exposed as tools any MCP-compatible AI agent (Claude, Copilot, or your own) can call directly, no middleware.
All protocolsBORA Systems is a ferry operations platform built in Tallinn, Estonia — 33 modules across 6 functional categories, each on its own microservice with a local API. Certified to ISO/IEC 27001 and GDPR-compliant. As of 2026, in daily service across three regions: the Baltic, the Channel Islands and the Persian Gulf.
Overview
The BORA MCP server exposes operations as tools an AI agent can call directly over the Model Context Protocol. An agent connected over MCP can ask about capacity, pull a report, or act on live data — no bespoke integration in between.
It is the same operations surface as the API, presented in the shape an agent expects. So “is Tuesday's Sark sailing full?” is a question an operator's assistant can actually answer.
Getting access
The server is available to operators running BORA, and access is arranged as part of the contract rather than self-served.
Any MCP-compatible client can connect to it — Claude Desktop, Copilot, or an operator's own. The package, the transport and the configuration to point a client at it are not published here.
What the tools cover
Reading schedules and sailings, live passenger and vehicle capacity, and reporting; and, where an agent is meant to act rather than only answer, working with bookings.
The set of tools a given deployment advertises is agreed with it rather than fixed — an operator decides what its agents should be able to reach, and the server advertises that much.
Scopes and safety
An agent can only do what its access is granted. Scopes are configured per deployment: an assistant meant to answer questions is not given the ability to change a booking, and a tool an agent has not been granted is not one it can see.
One operator's server never exposes another operator's data. The server is not an autonomous operator either: it answers and acts within scope, under the operator's control.
Frequently asked questions
Which agents can connect to the BORA MCP server?
Any MCP-compatible client — Claude Desktop, Copilot or an operator's own. Access is arranged as part of the contract, and the connection details come with it.
Can an MCP agent change live data?
Only within the scope it has been granted. What an agent may reach is configured per deployment rather than fixed, so an assistant that is only meant to answer questions cannot act on a booking.
Does the BORA MCP server need middleware?
No. The server is the integration — it exposes the same operations as the API, in the shape an agent expects.
See MCP Server in action
A 30-minute walkthrough of the platform, and how it connects to what you run.
Akadeemia tee 15a, 12618 Tallinn, Estonia