mcp -sqlite-npx
MCP server from johnnyoshika/mcp-server-sqlite-npx
claude mcp add --transport stdio johnnyoshika-mcp-server-sqlite-npx npx -y mcp-server-sqlite-npx /absolute/path/to/database.db \ --env PATH="/absolute/path/to/executables" \ --env NODE_PATH="/absolute/path/to/node_modules"
How to use
This MCP server provides an SQLite-backed implementation of the Model Context Protocol for Node.js environments. It runs via npx, offering an alternative to Python/UV-based runtimes, and is designed to be integrated with clients like Claude Desktop or MCP Inspector. To use it, configure Claude Desktop or your MCP client to invoke the server through npx with the appropriate database path as an argument. The server exposes the MCP endpoints over the standard protocol, enabling creation, retrieval, and manipulation of model-context data stored in the SQLite database. For testing, you can launch the server through the MCP Inspector tool by pointing it at your dist/index.js (or equivalent entry) and providing the path to your database. This setup allows you to exercise the MCP flow against a lightweight SQLite store without needing a Python runtime.
How to install
Prerequisites:
- Node.js and npm installed on your system.
- Access to npm (or npx) for executing the MCP server package.
Installation steps:
- Ensure dependencies are clean: npm ci
- Build the TypeScript source (if applicable): npm run build
- Verify installation by running a quick check or invoking the inspector: npx @modelcontextprotocol/inspector node dist/index.js /absolute/path/to/database.db
- When configuring clients (e.g., Claude Desktop), reference the npx command with the proper package and database path as described in the README. Example configuration snippet: { "mcpServers": { "sqlite": { "command": "/absolute/path/to/npx", "args": [ "-y", "mcp-server-sqlite-npx", "/absolute/path/to/database.db" ], "env": { "PATH": "/absolute/path/to/executables", "NODE_PATH": "/absolute/path/to/node_modules" } } } }
Additional notes
Environment variables: PATH and NODE_PATH can be important on systems where node modules or executables are located in non-standard directories. Ensure the database file path is accessible and writable by the process. If you encounter permissions issues, set appropriate file permissions for the SQLite database. When upgrading, bump the package version and re-run installation steps. For debugging, you can use MCP Inspector to send requests against dist/index.js and verify that operations against the /absolute/path/to/database.db work as expected. If using Claude Desktop, keep the config paths absolute to avoid runtime path resolution issues.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.