Automation library · Setup and learning

Build your own SQLite MCP server

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Model 5Logic 4

The steps in the order they run, from what starts it.

  1. 1When Executed by Another WorkflowExecute Workflow triggerStarts it
  2. 2DescribeTablesTool CodeModel
  3. 3ListTablesTool CodeModel
  4. 4CreateRecordsTool WorkflowModel
  5. 5UpdateRowsTool WorkflowModel
  6. 6ReadRowsTool WorkflowModel
  7. 7OperationSwitchLogic
  8. 8SQLite MCP ServerMcp triggerStarts it
  9. 9ReadRecordsCodeLogic
  10. 10CreateRecordCodeLogic
  11. 11UpdateRecordCodeLogic

How it's built

Starts on
An event in a connected app
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.