📌Overview

Purpose: To provide a Model Context Protocol server that facilitates interaction with the Glide API (version 1 and 2).

Overview: The Glide API MCP Server is designed to streamline the interaction with the Glide API, allowing developers to securely handle API requests and manage application data effectively. It features robust error handling and is built with a type-safe TypeScript implementation, ensuring that developers can integrate it seamlessly into their projects.

Key Features:

• Support for both Glide API v1 and v2: Enables compatibility with different versions of the Glide API, allowing for flexible integration.

• Secure API key handling through environment variables: Improves security by storing API credentials in environment variables, minimizing the risk of exposing sensitive information.

• Type-safe TypeScript implementation: Enhances development efficiency and reduces errors by ensuring type safety during integration and interaction with the API.

• Comprehensive error handling: Provides robust mechanisms for managing and reporting errors, improving the reliability and stability of applications utilizing the Glide API.

---

Glide API MCP Server

A Model Context Protocol server for interacting with the Glide API (v1 & v2).

Features

• Support for both Glide API v1 and v2
• Secure API key handling through environment variables
• Type-safe TypeScript implementation
• Comprehensive error handling

Available Tools

• set_api_version: Configure API version and authentication
• get_app: Get app information
• get_tables: List app tables
• get_table_rows: Get table data
• add_table_row: Add new row
• update_table_row: Update existing row

Secure Setup

1. Environment Variables

The server supports secure configuration through environment variables in the MCP settings file. Add your API credentials to the MCP settings file:

{
  "mcpServers": {
    "glide-api": {
      "command": "node",
      "args": ["path/to/build/index.js"],
      "env": {
        "GLIDE_API_KEY": "your-api-key-here",
        "GLIDE_API_VERSION": "v2"  // or "v1" for v1 API
      }
    }
  }
}

This keeps your API key secure by:

• Storing it in a configuration file rather than in code
• Keeping it out of version control
• Making it easy to update without modifying code

2. Runtime Configuration

You can also set or override the API version and key at runtime using the set_api_version tool:

use_mcp_tool({
  server_name: "glide-api",
  tool_name: "set_api_version",
  arguments: {
    version: "v2",
    apiKey: "your-api-key"
  }
});

Note: Runtime configuration overrides environment variables for the current session.

3. Security Best Practices

• Never commit API keys to version control
• Use environment variables in the MCP settings file
• Regularly rotate your API keys
• Set appropriate file permissions on the settings file

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Usage Examples

1. Get app information:

use_mcp_tool({
  server_name: "glide-api",
  tool_name: "get_app",
  arguments: {
    appId: "your-app-id"
  }
});

2. Add a row to a table:

use_mcp_tool({
  server_name: "glide-api",
  tool_name: "add_table_row",
  arguments: {
    appId: "your-app-id",
    tableId: "your-table-id",
    values: {
      column1: "value1",
      column2: "value2"
    }
  }
});