# Mobility API MCP server: n8n workflow template

> Started by an event in a connected app. It calls services over plain HTTP rather than through connectors.

Source: https://millionrounds.com/workflow/mobility-api-mcp-server (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Setup and learning](https://millionrounds.com/workflows?category=Setup+and+learning#library)

# Mobility API MCP server

Started by an event in a connected app. It calls services over plain HTTP rather than through connectors. 3 steps: small enough to read in one sitting and change without fear.

Small

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fmobility-api-mcp-server)

**3 steps** Small: readable in one sitting

**0** Branches: places the flow splits

**0** Loops or waits

**0** Services by connector: it calls them over plain HTTP

## The flow

Starts it 1 Service 2

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

- 1 **Retrieve Application Info** Http Request Tool *Service*
- 2 **Calculate Transit Route** Http Request Tool *Service*
- 3 **Mobility MCP Server** Mcp trigger *Starts it*

## How it's built

- **Starts on:** An event in a connected app
- **Steps:** 3
- **Size:** Small: readable in one sitting
- **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?

Not long. At 3 steps it can be read in one sitting and changed without fear.

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 3 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fmobility-api-mcp-server)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Workflows like it

Also setup and learning, with the same services where possible, closest in size first.

- [**Automated recipe finder** 3 steps](https://millionrounds.com/workflow/automated-recipe-finder)
- [**Call & SMS Twilio tool MCP server** 3 steps](https://millionrounds.com/workflow/call-and-sms-twilio-tool-mcp-server)
- [**Dropcontact tool MCP server** 3 steps](https://millionrounds.com/workflow/dropcontact-tool-mcp-server)
- [**Give AI agents power to create lists, items with LoneScale** 3 steps](https://millionrounds.com/workflow/give-ai-agents-power-to-create-lists-items-with-lonescale)
- [**Let AI agents get campaigns with Google Ads** 3 steps](https://millionrounds.com/workflow/let-ai-agents-get-campaigns-with-google-ads)
- [**Mocean tool MCP server both operations** 3 steps](https://millionrounds.com/workflow/mocean-tool-mcp-server-both-operations)