Query Bicycle Incident Data with BikeWise API through MCP Server

Complete MCP server exposing 4 BikeWise API v2 API operations to AI agents.

⚡ Quick Setup

1. Import this workflow into your n8n instance
2. Credentials Add BikeWise API v2 credentials
3. Activate the workflow to start your MCP server
4. Copy the webhook URL from the MCP trigger node
5. Connect AI agents using the MCP URL

🔧 How it Works

This workflow converts the BikeWise API v2 API into an MCP-compatible interface for AI agents.

• MCP Trigger: Serves as your server endpoint for AI agent requests
• HTTP Request Nodes: Handle API calls to https://bikewise.org/api
• AI Expressions: Automatically populate parameters via $fromAI() placeholders
• Native Integration: Returns responses directly to the AI agent

📋 Available Operations (4 total)

🔧 V2 (4 endpoints)

• GET /v2/incidents: Paginated incidents matching parameters
• GET /v2/incidents/{id}: GET /v2/incidents/{id}
• GET /v2/locations: Unpaginated geojson response
• GET /v2/locations/markers: Unpaginated geojson response with simplestyled markers

🤖 AI Integration

Parameter Handling: AI agents automatically provide values for:
• Path parameters and identifiers
• Query parameters and filters
• Request body data
• Headers and authentication

Response Format: Native BikeWise API v2 API responses with full data structure

Error Handling: Built-in n8n HTTP request error management

💡 Usage Examples

Connect this MCP server to any AI agent or workflow:

• Claude Desktop: Add MCP server URL to configuration
• Cursor: Add MCP server SSE URL to configuration
• Custom AI Apps: Use MCP URL as tool endpoint
• API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

• Zero Setup: No parameter mapping or configuration needed
• AI-Ready: Built-in $fromAI() expressions for all parameters
• Production Ready: Native n8n HTTP request handling and logging
• Extensible: Easily modify or add custom logic

🆓 Free for community use! Ready to deploy in under 2 minutes.