mcp-firebird is a server implementation of Anthropic's Model Context Protocol (MCP) specifically designed for Firebird SQL databases. It enables AI agents, such as Claude Desktop, to securely and efficiently interact with Firebird databases for various tasks including schema inspection, executing read-only or write SQL queries, analyzing table structures, and generating SQL from natural language descriptions. The package, currently at version 2.6.0, provides a robust interface to unlock valuable data in Firebird systems for AI-driven applications. It supports Server-Sent Events (SSE) for real-time data streaming and offers enhanced command-line parameter handling and environment variable configuration. Developed by PuroDelphi, it is actively maintained with ongoing feature enhancements and performance optimizations, making it a comprehensive toolkit for integrating Firebird with modern AI workflows. Key differentiators include its dedicated focus and comprehensive features for Firebird within the MCP ecosystem, offering more extensive management and analysis tools compared to simpler, older implementations.
npm install mcp-firebirdVerified import paths — ran on the pinned version, not inferred.
Demonstrates how to run the mcp-firebird server using `npx`, configuring it via both command-line arguments and environment variables for connecting to a Firebird database and enabling SSE transport.
Refer to the official MCP documentation and mcp-firebird release notes for compatibility details. Ensure that both the server and client adhere to the same MCP protocol version. Older MCP servers using `FastMCP` have been replaced by `McpServer` in newer SDKs.
Verify all connection parameters are correct. Ensure the Firebird database server is running and accessible from the machine hosting the mcp-firebird server. Double-check environment variables or CLI arguments for typos.
Ensure that the user running the mcp-firebird server (or the Docker container user) has appropriate read/write permissions to the Firebird database file and any associated data directories. Check permissions on `init.sql` and `test_db.sql` if used for database initialization.
Review your Dockerfile and Docker Compose configuration to ensure the Firebird database file is correctly mounted as a volume and the `DATABASE` environment variable points to the correct location within the container.
Set the `DATABASE` environment variable or `--database` CLI argument to the correct absolute path of your Firebird `.fdb` database file. For Docker, ensure the path reflects the location inside the container's filesystem after volume mounting.
Verify that the Firebird database server is active and listening on the specified host and port. Double-check the `FIREBIRD_HOST`, `FIREBIRD_PORT`, `FIREBIRD_USER`, and `FIREBIRD_PASSWORD` environment variables or their CLI counterparts for accuracy. Check firewall rules.
Adjust file system permissions for the Firebird database file and its parent directory to grant read and write access to the user account or group under which the mcp-firebird process is running.
No dependency data recorded yet.