- Home
- MCP servers
- MCP SQLite
MCP SQLite
- typescript
0
GitHub Stars
typescript
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"mcp-mirror-johnnyoshika_mcp-server-sqlite-npx": {
"command": "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"
}
}
}
}The MCP SQLite Server provides a Node.js implementation of the Model Context Protocol SQLite server. It lets you run a local SQLite-based MCP server that CLAUDE Desktop or other clients can query and manage, enabling fast development and testing without needing a full Python environment. This guide walks you through using, installing, and configuring the server for local development and client integration.
How to use
You connect to the MCP SQLite Server from an MCP client by running the server locally and pointing your client at the local database file you provide. Use the standard client configuration to specify the server executable and the path to your database file. Typical workflows include running a local server instance during development, then configuring your client (such as Claude Desktop) to connect to it via the local command and database path.
How to install
Prerequisites: ensure you have Node.js and npm installed on your system. You will also need npx for running package executables in some workflows.
Install via Smithery for Claude Desktop automation:
npx -y @smithery/cli install mcp-server-sqlite-npx --client claude
Manual configuration for Claude Desktop
Add the MCP server configuration to Claude Desktop so it can launch the MCP SQLite Server and connect to your database.
{
"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"
}
}
}
}
Full example using a Node version manager
If you manage Node with a tool like nvm, use an explicit path to the node and npx binaries along with your database path.
{
"mcpServers": {
"sqlite": {
"command": "/Users/johnny/.nvm/versions/node/v22.12.0/bin/npx",
"args": [
"-y",
"mcp-server-sqlite-npx",
"/Users/johnny/projects/database.db"
],
"env": {
"PATH": "/Users/johnny/.nvm/versions/node/v22.12.0/bin:/usr/local/bin:/usr/bin:/bin",
"NODE_PATH": "/Users/johnny/.nvm/versions/node/v22.12.0/lib/node_modules"
}
}
}
}
Development
To build and test the server locally during development, follow these steps.
npm ci
npm run build
Testing with MCP Inspector
You can verify the server works by launching it with MCP Inspector and pointing it at your database file.
npx @modelcontextprotocol/inspector node dist/index.js /absolute/path/to/database.db
Testing with Claude Desktop
Configure Claude Desktop to connect to the local server by adding the MCP entry for the sqlite server and pointing to the local node executable and the server script.
{
"mcpServers": {
"sqlite": {
"command": "/absolute/path/to/node",
"args": [
"/absolute/path/to/index.js",
"/absolute/path/to/database.db"
]
}
}
}
Publish
When you’re ready to release a new version, update the version in package.json, install dependencies, and commit with a release message.
Available tools
inspector
MCP Inspector tool trajectory to validate the server by launching the compiled dist/index.js with a database file path.
claude_desktop_integration
Guide Claude Desktop to connect to the local MCP server using the mcpServers configuration and a local database file.