Glide to n8n MCP Adapter

Name: Glide to n8n MCP Adapter
Author: mows21

@mows21

Repository

About Glide to n8n MCP Adapter

MCP server that connects Glide API requests to n8n workflows using the Model Context Protocol

#glide #n8n #mcp-adapter

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "glide-n8n-mcp-adapter": {
      "command": "python",
      "args": [
        "-m",
        "venv",
        "venv"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Glide to n8n MCP Adapter?

Glide to n8n MCP Adapter is an MCP server that bridges Glide API requests to n8n workflows. It allows AI assistants like Claude and GPT‑4 to trigger n8n workflows and interact with Glide apps through a standard MCP interface.

How to use Glide to n8n MCP Adapter?

Run with Docker Compose (recommended): clone the repo, copy .env.example to .env and set your n8n webhook URL, then run docker-compose up -d. Alternatively, set up manually with Python 3.9+, create a virtual environment, install dependencies, configure .env, and run python glide_n8n_adapter.py (stdin/stdout) or HTTP_ADAPTER=true python http_adapter.py (HTTP mode).

Key features of Glide to n8n MCP Adapter

Bridges Glide API operations to n8n workflows
Provides tools for discovering and managing n8n workflows
Supports executing n8n workflows with parameters
Offers specialized tools for common Glide operations
Works with both stdin/stdout and HTTP modes
Includes Docker support for easy deployment

Use cases of Glide to n8n MCP Adapter

AI assistants triggering n8n workflows to read or modify Glide app data
Managing available n8n workflows (list, search, add, remove) via conversational commands
Executing custom n8n workflows for Glide row operations (get, create, update, delete)
Integrating Claude Desktop or other MCP clients with Glide and n8n

FAQ from Glide to n8n MCP Adapter

What dependencies are required to run the adapter?

You need an n8n instance with the MCP workflow running and its webhook URL, plus Python 3.9+ (or Docker and Docker Compose for containerized deployment).

How does the adapter connect to my n8n instance?

It uses the webhook URL of your n8n MCP server workflow, which you set in the N8N_WEBHOOK_URL environment variable in the .env file.

Can the adapter run in HTTP mode instead of stdin/stdout?

Yes, set the environment variable HTTP_ADAPTER=true and run http_adapter.py. The HTTP server listens on port 3000 by default (configurable via PORT).

What Glide operations are available through the adapter?

The adapter provides tools to get, create, update, and delete rows in a Glide table. These operations can be mapped to specific n8n workflows using optional environment variables for workflow IDs.

How do I add custom n8n workflows for Glide operations?

Create a workflow in n8n with an "Execute Workflow Trigger" node, define the input schema, implement Glide API calls via HTTP Request nodes, tag the workflow with "mcp", and activate it. The adapter will discover and manage these workflows.