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).
@mows21
Basic information
MCP server that connects Glide API requests to n8n workflows using the Model Context Protocol
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"glide-n8n-mcp-adapter": {
"command": "python",
"args": [
"-m",
"venv",
"venv"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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).
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).
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.
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`).
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.
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.

Know when your AI agents, cron jobs and CI pipelines fail, stall or go quiet. Your agent sets up monitors from a plain description, tells you what is broken and why, reads run history and traces, and writes notes on inci

AI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.
MCP server that lets Claude Code, Cursor or Codex ask you for API keys on a local page and write them to .env. The agent only ever sees key names.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
Comments