Mobility API MCP Server for AI Agents

Transforms Mobility API into an MCP-compatible server, exposing transit and info operations for easy AI agent integration via n8n webhooks.

n8n
Mobility API MCP Server for AI Agents

This n8n workflow creates a fully functional MCP (Model Context Protocol) server that bridges the Mobility API (from O2 developer sandbox) to AI agents. It handles two key operations: retrieving application info via GET /info and transit data between locations via GET /transit/{from}/{to}. The MCP Trigger node serves as the endpoint, while HTTP Request nodes manage API calls, automatically populating parameters with AI-provided data using $fromAI() expressions. Native error handling ensures robust responses back to the AI agent.

Benefits include rapid setup for AI-driven mobility queries without custom coding—import, add credentials, activate, and share the webhook URL. It saves hours of development time by providing a standardized MCP interface, enabling seamless integration with tools like Claude Desktop, Cursor, or custom AI apps. Ideal for e-commerce customer service scenarios involving transit planning, delivery routing, or location-based services.

Use cases span logistics automation, where AI agents fetch real-time transit info for order fulfillment; customer support bots querying mobility data; or developer tools for testing AI agents with real APIs. Supports path parameters, queries, and full response structures, making it versatile for scalable AI workflows.

$14.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related E-commerce workflows

More from Jordi Faber

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.