Research date: 2026-09-17 UTC Scope: Options that can expose Derby application capabilities to MCP hosts, plus maintained vendor MCP servers worth connecting alongside the app.
Do not install a generic database or filesystem MCP server as the Derby integration. Add a thin MCP surface to the existing Node process and call the same domain/service functions the Derby routes already use.
Recommended default: the official MCP TypeScript SDK v2, with the official Express middleware package, mounted at /mcp beside the existing Derby routes. It is the least speculative dependency, is Tier 1 in the MCP SDK matrix, runs on Node.js, and has first-party adapters for Express, Fastify, Hono, and Node HTTP.