Glide to n8n MCP Adapter

Created By
mows21a year ago
MCP server that connects Glide API requests to n8n workflows using the Model Context Protocol
Overview

What is Glide to n8n MCP Adapter?

The Glide to n8n MCP Adapter is a server that connects Glide API requests to n8n workflows using the Model Context Protocol (MCP). It enables AI assistants to trigger workflows and interact with Glide apps seamlessly.

How to use Glide to n8n MCP Adapter?

To use the adapter, you can either deploy it using Docker or set it up manually. For Docker, clone the repository, configure the .env file with your n8n webhook URL, and run it using Docker Compose. For manual setup, create a virtual environment, install dependencies, and run the adapter script.

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 workflows with parameters.
  • Offers specialized tools for common Glide operations.
  • Works with both MCP protocol and HTTP APIs.
  • Includes Docker support for easy deployment.

Use cases of Glide to n8n MCP Adapter?

  1. Automating data operations in Glide apps through n8n workflows.
  2. Integrating AI assistants like Claude and GPT-4 with Glide applications.
  3. Managing and executing workflows for various Glide API operations.

FAQ from Glide to n8n MCP Adapter?

  • What is the Model Context Protocol?

The Model Context Protocol is a standard interface that allows AI assistants to interact with various applications and services.

  • Is Docker required to run the adapter?

No, Docker is optional. You can run the adapter manually using Python as well.

  • What are the prerequisites for using this adapter?

You need an n8n instance with the MCP workflow running, the webhook URL for the n8n MCP workflow, and Python 3.9+ if not using Docker.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mows21
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago