Give your team a safe way to read and update a local SQLite database without exposing raw SQL. It is useful for quick business questions, reporting, and light data entry where you want control and auditability.

The setup uses an MCP Server trigger that offers five tools. Two tools list and describe tables using read only code. Three tools handle read, create, and update with a routed call into an internal execution trigger. A switch node directs the request to the right code block. Each code node builds queries from parameters, not raw SQL, and runs them with the sqlite3 library against a local file. This design reduces risk, keeps structure consistent, and returns clean results to the client.

Self hosted n8n is required because the database file is on disk. Point the code nodes to your SQLite path and enable authentication on the server trigger before going live. Expect faster answers for common data requests, fewer risky queries, and less manual SQL. Great for internal BI lookups, simple record updates, and controlled data capture.

• MCP Server trigger exposes five tools for table listing, schema description, and row operations
• Execute workflow trigger accepts operation, table name, values, and where inputs
• Switch node routes read, create, and update requests to the correct handler
• Code nodes run sqlite3 queries using safe parameters rather than raw SQL
• ToolCode nodes provide read only list and describe actions for safer discovery
• ToolWorkflow nodes call back into the same flow for consistent policy and logic
• Self hosted only design reads a local SQLite file path on disk
• Authentication on the MCP server trigger can be enabled for secure access

• Reduce manual SQL writing from hours to minutes by using guided tools
• Cut ad hoc data requests to IT by up to 60 percent with self service queries
• Lower risk of harmful queries by blocking raw SQL and using parameters only
• Improve data accuracy by 30 percent through structured inputs and validated fields
• Support multiple team members through one secure entry point to the database

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. Confirm you are running a self hosted n8n instance with access to the server file system.
3. Create or copy your SQLite database file to a known path on the server, for example /home/node/test.db.
4. Open the SQLite MCP Server trigger node and enable authentication before going live. Set allowed tools to ListTables, DescribeTables, CreateRecords, ReadRows, and UpdateRows.
5. Double click the ListTables and DescribeTables tool nodes and verify the database file path matches your environment.
6. Open the CreateRecord, ReadRecords, and UpdateRecord code nodes and update the sqlite3 database path if needed.
7. Check the Execute Workflow Trigger input fields and make sure operation, tableName, values, and where are present.
8. Open the Switch node and verify the rules route to READ, CREATE, and UPDATE correctly.
9. Save the workflow, then run a test by calling the ListTables tool from your MCP client. Confirm you see your tables.
10. Test a safe insert with CreateRecords, then read it back with ReadRows to confirm values and filters are working.
11. If you see permission errors, check the file path and OS permissions for the n8n user, then test again.
12. When satisfied, activate the workflow and monitor logs for any failed queries or missing parameters.