Repository navigation
mcp-firebird 2.12.2
MCP Firebird 2.12.2
October 17, 2026. Compatibility correction on top of 2.12.1: existing users receive the pre-2.12.1 date representation without configuring anything. The BLOB/transaction, SQL, metadata and tool-count fixes remain included.
Backward-compatible dates by default
The pure-JavaScript driver path once again preserves JavaScript Date objects internally. Existing JSON, tool and resource serialization emits ISO 8601 UTC strings with T and Z, just as before 2.12.1. No stored Firebird values are changed, no SQL is replayed, and no date-parser migration is required when upgrading from 2.12.0 or earlier for this fix.
The zone-free format introduced in 2.12.1 is now opt-in through the process environment:
# Optional; leave unset or use iso for historical output.
FIREBIRD_DATE_FORMAT=wall-clock- Unset, empty/whitespace, or
iso: historical ISO/UTC JSON output. wall-clock:YYYY-MM-DD HH:mm:ss.SSS, preserving the driver's local date/time fields without a zone suffix.- Other values: reject the pure-JS query before application SQL/transaction dispatch. Each query captures its mode before dispatch; change the owning launcher and restart the MCP process to apply a new setting consistently.
This is not a security-policy field or client-supplied HTTP parameter. Merge the variable into your existing MCP launcher's env without replacing connection/authentication settings. The supplied Compose example forwards ${FIREBIRD_DATE_FORMAT:-iso}; configure Compose's environment and recreate the MCP container when changing it. Do not alter/restart Firebird or migrate your database to change response formatting.
Users who adapted clients to 2.12.1's zone-free output can explicitly select wall-clock to keep that representation. Other users need no new date setting. Read the configuration examples and Spanish summary.
Scope and preserved behavior
- No native-driver date or generic tool Date/Buffer serialization changes. The date setting only affects pure-JS database row Date columns; existing BLOB decoding is retained.
- Preserve transaction-owned BLOB reads, single SQL execution, commit-error propagation, configured deadlines and cleanup ownership. Authorized writes and auditing keep their existing transaction behavior.
- Retain the SQL syntax fixes and nested permission checks, complete column descriptions, honest unavailable-plan errors and registered tool counts from 2.12.1.
- Advanced controls and strict HTTP mode remain opt-in. Firebird driver dependencies, Node.js 20.19+ minimum and the npm
alphatag are unchanged. GitHub Actions remains disabled. - This restores an output contract, not every driver date limitation: millisecond precision, timezone interpretation and driver DATE/TIME synthetic components remain applicable. Neither mode adds timezone-aware Firebird type support.
Install
npm install -g mcp-firebird@latestOr pin mcp-firebird@2.12.2 in an existing npx launcher. Keep the connection/transport/security configuration and restart the MCP process.
Validation
- Targeted tests passed default/blank/explicit ISO and wall-clock modes, invalid configuration before application dispatch, captured mode, unchanged generic/native serialization, and DATE/TIME/TIMESTAMP wire decoding in UTC, Istanbul, Bogota and New York (winter/summer fixtures).
- Client output checks cover SDK 1 and SDK 2 legacy/2026 over STDIO and loopback HTTP in both date modes with real production policy, query/transaction and tool paths plus a controlled driver boundary. They are not a live native-driver test.
- Fresh disposable live integration passed on Firebird 2.5.9 with the pure-JS driver, including both date representations and the earlier BLOB, SQL-policy, metadata, plan non-execution, audit, authorized-write and event/reconnect regressions. The temporary database and audit file were removed.
- The full local release gate passed type checking, a fresh build, lint error checks, 1,292 unit tests, 110 protocol/Node tests with no skips, and compiled security-runtime checks. Production dependency audit reports zero known vulnerabilities in the tested lockfile, not an all-development-dependencies or future-vulnerabilities guarantee.
prepublishOnlyruns the gate again without bypassing it. No live Firebird 3/4/5 or native-driver coverage is claimed.
Full changelog · English date guide · Configuración en español