Swagger2OpenAPI Converter MCP Server

Nodes

⚡ Quick Setup

Import this workflow into your n8n instance
Credentials Add Swagger2OpenAPI Converter credentials
Activate the workflow to start your MCP server
Copy the webhook URL from the MCP trigger node
Connect AI agents using the MCP URL

🔧 How it Works

This workflow converts the Swagger2OpenAPI Converter 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://mermade.org.uk/api/v1
• AI Expressions: Automatically populate parameters via $fromAI() placeholders
• Native Integration: Returns responses directly to the AI agent

📋 Available Operations (6 total)

🔧 Badge (1 endpoints)

• GET /badge: Redirect to Badge SVG

🔧 Convert (2 endpoints)

• GET /convert: Convert Swagger in Body
• POST /convert: Convert a Swagger 2.0 definition passed in the body to OpenAPI 3.0.x

🔧 Status (1 endpoints)

• GET /status: Check API Status

🔧 Validate (2 endpoints)

• GET /validate: Validate OpenAPI in Body
• POST /validate: Validate an OpenAPI 3.0.x definition supplied in the body of the request

🤖 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 Swagger2OpenAPI Converter 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