analyze-missing-indexes
Analyzes a SQL query to identify missing indexes that could improve performance
LABSCO SUMMARY
A Firebird connection that also hands over the database's stored code and its event stream, not just its tables.
Most database servers stop at tables and queries; this one reads triggers, procedures, functions and packages back with their source, which is where the business logic in a long-lived Firebird database actually lives. The event subscription is the other distinctive piece — an agent can wait on a POST_EVENT the database already fires instead of re-running a query on a timer.
What it is
A Firebird SQL server covering three jobs: running queries, reading the database's own metadata and source code, and subscribing to Firebird's native POST_EVENT notifications.
What you get
- SQL execution with Firebird's own FIRST/ROWS pagination, plus a batch call that runs several queries in parallel
- Table listing, detailed schemas, stored field descriptions, and filtered, ordered, paginated reads of table data
- Schemas for many tables at once, and per-table statistics covering row count, column stats and data distribution
- Stored code read back with its source: triggers with their table and state, stored procedures with their parameters, PSQL and UDF functions, and packages with header and body
- Query tuning without leaving the conversation: the execution plan, a timing run that repeats the query, and an analysis of which missing indexes would help
- Event subscription over Firebird's POST_EVENT, so the agent is notified when a trigger fires instead of polling
- Housekeeping reads: database and server information, a health check on the connection, the available events, and per-tool help
- A wire-encryption check on the live connection, when running on the native driver
Requirements
A reachable Firebird database and its credentials, set through FIREBIRD_HOST, FIREBIRD_PORT, FIREBIRD_DATABASE, FIREBIRD_USER and FIREBIRD_PASSWORD, or the equivalent command-line flags. Published on npm as mcp-firebird. Two transports: stdio for a local client, or Streamable HTTP with TRANSPORT_TYPE=sse and SSE_PORT for remote clients such as n8n. FIREBIRD_API_KEY turns on Enterprise Managed Authorization, where the client sends a bearer token and the real database password stays on the server. Wire encryption needs the native driver, which must be installed globally alongside the server — npx cannot reach globally installed modules — and WireCrypt has to be set in firebird.conf on the server first.
Setup effort
One command plus credentials — npx -y mcp-firebird --database=<YOUR_PATH_TO_DATABASE>, then supply credentials
USE CASES
01
Getting oriented in a database you inherited
List the tables, pull schemas for a batch of them at once, and read the stored field descriptions the original team left behind.
02
Finding out why a report query is slow
Read the execution plan, time the query over repeated runs, and get the missing indexes that would change it.
03
Understanding logic that lives inside the database
List the triggers, procedures and functions, then read the source of the ones involved in the behaviour you are chasing.
04
Reacting when the database changes, without polling
List the events the triggers already post, subscribe to the one you care about, and let the notification arrive.
05
Answering a data question directly
Pull a filtered, ordered page of a table, or write the SQL yourself when the question needs a join.
06
Checking the connection is what you think it is
Read the database and server details, run the health check, and confirm whether the link is wire-encrypted.
27 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
analyze-query-performance
Analyzes the performance of a SQL query by executing it multiple times and measuring execution time
analyze-table-statistics
Analyzes statistical information about a table including row count, column statistics, and data distribution.
describe-batch-tables
Gets the detailed schema of multiple tables in parallel for improved performance.
describe-function
Obtiene información detallada sobre una función específica incluyendo su código fuente (si es PSQL function)
describe-package
Obtiene información detallada sobre un paquete específico incluyendo su header y body source
describe-procedure
Obtiene información detallada sobre un procedimiento almacenado específico incluyendo su código fuente y parámetros
describe-table
Gets the detailed schema (columns, types, etc.) of a specific table.
describe-trigger
Obtiene información detallada sobre un trigger específico incluyendo su código fuente, tipo, secuencia y estado
execute-batch-queries
Executes multiple SQL queries in parallel for improved performance.
execute-query
Executes a SQL query in the Firebird database. Uses FIRST/ROWS for pagination.
get-database-info
Retrieves general information about the connected Firebird database.
get-execution-plan
Gets the execution plan for a SQL query to understand how the database will execute it
get-field-descriptions
Gets the stored descriptions for fields of a specific table (if they exist).
get-server-info
Obtiene información sobre el servidor MCP Firebird y las herramientas disponibles
get-table-data
Retrieves data from a specific table with optional filtering, pagination, and ordering.
get-tool-help
Obtiene información detallada sobre una herramienta específica
list-available-events
Lista los eventos nativos (POST_EVENT) disponibles en los triggers y procedimientos de la base de datos
list-available-tools
Lista todas las herramientas disponibles en el servidor MCP
list-functions
Lista todas las funciones en la base de datos (UDFs y PSQL functions)
list-packages
Lista todos los paquetes en la base de datos (disponible en Firebird 3.0+)
list-procedures
Lista todos los procedimientos almacenados en la base de datos con información sobre parámetros de entrada/salida
list-tables
Lists all user tables in the current Firebird database.
list-triggers
Lista todos los triggers en la base de datos con información sobre tabla asociada, tipo de trigger y estado
subscribe_to_event
Subscribe to a Firebird event (POST_EVENT) to receive proactive notifications
system-health-check
Verifica el estado de salud del sistema y la conectividad de la base de datos
verify-wire-encryption
Verifies if the current database connection is using wire encryption (requires native driver).
BEFORE YOU INSTALL
What to know first
Tools you get
27 tools when we connected; the project documents 30. backup-database, restore-database and validate-database need the Firebird client tools installed. ping, echo, get-methods and describe-method in the tool docs appear outdated; the server offers list-available-tools and get-tool-help instead.
Requires
- Node.js (npx), or a global npm install for the HTTP server
- A Firebird database — its path, user and password go in the command arguments (--database, --user, --password), or in FIREBIRD_PASSWORD when you run the HTTP server yourself
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y mcp-firebird --database=<YOUR_PATH_TO_DATABASE>MCP Clients
Claude Desktop, GitHub Copilot
JSON
{
"mcpServers": {
"mcp-firebird": {
"command": "npx",
"args": [
"-y",
"mcp-firebird",
"--database",
"<YOUR_PATH_TO_DATABASE>",
"--host",
"localhost",
"--port",
"3050",
"--user",
"SYSDBA",
"--password",
"masterkey"
]
}
}
}n8n
On the machine that can reach your database, start the server over HTTP. masterkey in the block is a sample database password; yours is your Firebird database password. <YOUR_FIREBIRD_API_KEY> is a token you choose — it is the bearer n8n sends below:
N8N · TERMINAL
npm install -g mcp-firebird
export TRANSPORT_TYPE=sse
export SSE_PORT=3003
export FIREBIRD_PASSWORD=masterkey
export FIREBIRD_API_KEY=<YOUR_FIREBIRD_API_KEY>
mcp-firebird --database <YOUR_PATH_TO_DATABASE> --user SYSDBAThen in n8n: add a new MCP Server Connection, choose HTTP / SSE as the transport type, set the Server URL to http://YOUR_SERVER_IP:3003/mcp, and under Headers add Key: Authorization, Value: Bearer <YOUR_FIREBIRD_API_KEY>.
