Glide MCP Server

Created By
mows21a year ago
Model Context Protocol (MCP) server for Glide Apps API v2 - enables AI assistants to interact with Glide Apps
Overview

What is Glide MCP Server?

Glide MCP Server is a Model Context Protocol (MCP) server designed for interacting with the Glide Apps API v2, enabling AI assistants to communicate with Glide Apps through a standardized interface.

How to use Glide MCP Server?

To use Glide MCP Server, you can set it up using one of three methods: One-Click Setup, Manual Setup with Docker Compose, or Docker Run. Each method involves cloning the repository, configuring your Glide API key, and running the server.

Key features of Glide MCP Server?

  • Supports both standard Glide Tables API and Glide Big Tables API v2.
  • Handles datasets up to 10 million rows with Big Tables support.
  • Offers features like stashing for large data uploads and pagination for large datasets.
  • Multiple deployment options including Docker and local setups.
  • Provides an HTTP adapter for services requiring HTTP endpoints.

Use cases of Glide MCP Server?

  1. Enabling AI assistants to manage and interact with Glide Apps.
  2. Handling large datasets efficiently with pagination and stashing.
  3. Integrating with various tools like Claude Desktop and RooCode for enhanced functionality.

FAQ from Glide MCP Server?

  • What is the maximum dataset size supported?

Glide MCP Server supports datasets up to 10 million rows with the Big Tables API.

  • Is there a recommended setup method for beginners?

Yes, the One-Click Setup is recommended for beginners for ease of use.

  • Can I use Glide MCP Server without Docker?

Yes, you can set it up locally without Docker using the manual setup instructions.

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

Recommend Servers

View All
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