Node MCP Server

Pure JavaScript and Asynchronous Firebird client for Node.js.

Local serverstdioTypeScript

What is the Node MCP server?

Pure JavaScript and Asynchronous Firebird client for Node.js. Exposed over MCP by the node mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

[NPM version][npm-version-image]][npm-url] [NPM downloads][npm-downloads-image]][npm-url] [Mozilla License][license-image]][license-url]

Its toolset

Everything the assistant can do here goes through one of these:

  • Methods — The Methods tool exposed by this server
  • Classic — // db = DATABASE db.query('SELECT * FROM TABLE', function (err, result) { // IMPORTANT: close the connection db.detach; }); });
  • Pooling — // Get a free pool pool.get(function (err, db) { if (err) throw err;

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at node-firebird on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 2 environment variables: FIREBIRD_HOST, DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Node's toolset — Methods, Classic, Pooling — is a fair guide to whether it matches your workflow. It is maintained by mariuz; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Node's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the node mcp server does with a few real requests.

Available tools

ToolWhat it does
MethodsThe Methods tool exposed by this server.
Classic// db = DATABASE db.query('SELECT * FROM TABLE', function (err, result) { // IMPORTANT: close the connection db.detach(); }); });
Pooling// Get a free pool pool.get(function (err, db) { if (err) throw err;

How to install the Node MCP server

{
  "mcpServers": {
    "firebird": {
      "command": "npx",
      "args": ["-y", "node-firebird"],
      "env": {
        "FIREBIRD_HOST": "your-value",
        "DATABASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
FIREBIRD_HOSTEndpoint or connection string the server talks to.Optional
DATABASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Node to Methods.
  • Use Node to Classic.
  • Use Node to Pooling.

Frequently asked questions

It connects Node to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Methods, Classic, Pooling) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Node directly.