Skip to main content
Glama
Glide API MCP Server

Glide API MCP Server

by knmurphy

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

Related MCP server: Placid MCP Server

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 approach 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

While environment variables are the recommended way to configure the server, 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: The runtime configuration will override any environment variables for the current session.

3. Security Best Practices

  1. Never commit API keys to version control

  2. Use environment variables in the MCP settings file

  3. Regularly rotate your API keys

  4. 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"
  }
});
  1. 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"
    }
  }
});

Available Tools

6 tools
add_table_rowC

Add a new row to a table in a Glide app

Inputs: appId (required), tableId (required), values (required).

get_appC

Get information about a Glide app

Inputs: appId (required).

get_table_rowsC

Get rows from a table in a Glide app

Inputs: appId (required), tableId (required), limit, offset.

get_tablesC

Get tables for a Glide app

Inputs: appId (required).

set_api_versionB

Set the Glide API version and authentication to use

Inputs: apiKey (required), version (required).

update_table_rowC

Update an existing row in a table

Inputs: appId (required), rowId (required), tableId (required), values (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: add_table_row and update_table_row handle row modifications, get_table_rows and get_tables retrieve data, get_app provides app metadata, and set_api_version manages configuration. The descriptions make it easy to differentiate between table-level and row-level operations.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming: add_table_row, get_app, get_table_rows, get_tables, set_api_version, update_table_row. The verbs (add, get, set, update) are appropriately chosen and applied consistently across the toolset.

    Tool Count5/5

    With 6 tools, this server is well-scoped for interacting with Glide apps and tables. The count is appropriate for the domain, covering essential CRUD operations (add, get, update for rows), metadata retrieval (app and tables), and configuration (API version), without being overwhelming or insufficient.

    Completeness4/5

    The toolset provides good coverage for core Glide operations: CRUD for table rows (add, get, update), app and table metadata retrieval, and API configuration. A minor gap is the lack of a delete_table_row tool, which could limit full lifecycle management, but agents can work around this with updates or other methods.

    Related MCP Connectors

    Related MCP Servers