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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago