20. Firebird MCP Server

Once you connect your Firebird MCP database to your agent (including legacy line-of-business systems): the agent queries data via SQL and explores the schema, connecting over the native Firebird protocol (no ODBC(Open Database Connectivity) needed).

What it can do

• Run (read-only) SQL queries on tables and views

• Explore the schema: tables, views, stored procedures, columns and relations

• Produce answers, counts and summaries from business data

Examples

"Give me everything customer X did in the last 18 months: courses, hours, dates, people and trainer." "How many courses were delivered by area in the last quarter?"

Configuration parameters

The connector links to the Firebird server with the parameters below. A dedicated read-only user and purpose-built views optimised for the agents' questions are recommended.

Parameter	Required	Description
FIREBIRD_HOST	Yes	Hostname or IP of the Firebird server, reachable by AIsuru.
FIREBIRD_PORT	No	Firebird port (default: 3050).
FIREBIRD_DATABASE	Yes	Path or alias of the .fdb file on the Firebird server (e.g. /var/lib/firebird/data/gestionale.fdb).
FIREBIRD_USER	Yes	Firebird user. A dedicated read-only user is recommended.
FIREBIRD_PASSWORD	Yes	Firebird user password.
FIREBIRD_ROLE	No	Optional Firebird role (e.g. RDB$ADMIN), if required by your database setup.

Custom parameters

No additional parameters needed.

Note: the Firebird server must be reachable from AIsuru (directly with our IPs whitelisted, or via a tunnel). Alternatively the MCP can run inside the customer's network and be exposed as an HTTP MCP endpoint. Firebird syntax: to limit rows use FIRST n / ROWS n (not LIMIT).