Automation library · Setup and learning

Metabase tool MCP server all 10 operations

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

Medium

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

The flow

Starts it 1Service 10

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

  1. 1Get an alertMetabase ToolService
  2. 2Get many alertsMetabase ToolService
  3. 3Add a databasesMetabase ToolService
  4. 4Get many databasesMetabase ToolService
  5. 5Get Fields a databasesMetabase ToolService
  6. 6Get a metricMetabase ToolService
  7. 7Get many metricsMetabase ToolService
  8. 8Get a questionsMetabase ToolService
  9. 9Get many questionsMetabase ToolService
  10. 10Get the results from a questionMetabase ToolService
  11. 11Metabase Tool MCP ServerMcp triggerStarts it

How it's built

Starts on
An event in a connected app
Steps
11
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.