Get the FREE Ultimate OpenClaw Setup Guide →

glide-api

Model Context Protocol (MCP) server for @glideapps API

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio knmurphy-glide-api-mcp-server node path/to/build/index.js \
  --env GLIDE_API_KEY="your-api-key-here" \
  --env GLIDE_API_VERSION="v2"

How to use

Glide API MCP Server provides a set of tools to interact with the Glide API (v1 and v2) through a secure, model-context-driven interface.

The server exposes tools such as set_api_version to configure which version of the Glide API to use and to supply your API key, get_app to retrieve information about your Glide app, get_tables to list tables within an app, get_table_rows to fetch rows from a table, add_table_row to insert a new row, and update_table_row to modify existing rows. You can invoke these tools via the MCP runtime helper use_mcp_tool, specifying the server name (glide-api), the tool name, and the required arguments. Runtime configuration can override environment variables for the current session if needed.

Typical usage involves configuring your credentials securely in the MCP settings file, then calling the tools with the appropriate arguments to interact with your Glide data. For example, you can query app information, list tables, and perform CRUD operations on table data while keeping API keys out of source control.

How to install

Prerequisites:

  • Node.js (recommended LTS) and npm installed
  • Access to the repository where the Glide API MCP server will run

Installation steps:

  1. Install dependencies
npm install
  1. Build the server
npm run build
  1. (Optional) Run in development mode with auto-rebuild
npm run watch
  1. Prepare your MCP settings with secure environment variables for Glide API credentials (see environment variables section below) and start using the server via the MCP bridge or your orchestrator.

Additional notes

Environment variables: In the MCP settings, provide secure credentials for the Glide API, such as GLIDE_API_KEY and GLIDE_API_VERSION. Never commit keys to version control.

Runtime overrides: You can override API version and key at runtime using the set_api_version tool; this will take precedence for the current session.

Common issues: Ensure the path to the built index (path/to/build/index.js) is correct after your build step. If you encounter authentication errors, verify that the GLIDE_API_KEY and GLIDE_API_VERSION match the Glide API you intend to use (v1 or v2).

Security: Regularly rotate API keys and limit permissions to the minimum required for your app. Use file permissions and secret-scoped settings to keep credentials secure.

Related MCP Servers

Sponsor this space

Reach thousands of developers