Glide Platform Connector Service Endpoint

This Model Context Protocol (MCP) endpoint is engineered for bidirectional communication with the Glide Application Programming Interface (API), supporting both its initial specification (v1) and the subsequent iteration (v2).

Core Capabilities

• Dual compatibility for Glide API specifications v1 and v2.
• Secure handling of proprietary API access tokens via system environment variables.
• Implementation leveraging strongly typed TypeScript for reliability.
• Robust mechanisms for capturing and reporting operational failures.

Exposed Operational Functions

• set_api_version: Establishes the target API revision and configures requisite authentication credentials.
• get_app: Retrieves high-level configuration details pertinent to a specified application instance.
• get_tables: Enumerates all structural schemas (tables) associated with an application.
• get_table_rows: Fetches the dataset residing within a particular table.
• add_table_row: Inserts a novel record into a designated data structure.
• update_table_row: Modifies the content of an existing record within a table.

Credential Provisioning Strategy

1. Environmental Configuration Method

The preferred method for securing the access key involves declaring necessary variables within the MCP configuration manifest. Update the specific server block in your global settings:

{ "mcpServers": { "glide-api": { "command": "node", "args": ["path/to/build/index.js"], "env": { "GLIDE_API_KEY": "your-highly-secret-access-token", "GLIDE_API_VERSION": "v2" // Select 'v1' if interfacing with the legacy specification } } } }

This pattern upholds security standards by: - Isolating sensitive credentials from compiled application logic. - Preventing inadvertent inclusion within source control repositories. - Streamlining credential rotation procedures.

2. Dynamic Session Adjustment

Although environmental setup is strongly advocated, operational contexts require the flexibility to overwrite authentication parameters during active execution using the set_api_version utility:

typescript invoke_mcp_utility({ endpoint_identifier: "glide-api", procedure_name: "set_api_version", parameters: { version: "v2", apiKey: "a-temporary-runtime-key-for-this-session" } });

Observe that any parameter supplied dynamically at runtime will supersede configurations inherited from the static environment variables for the duration of that single execution thread.

3. Security Mandates

1. API secret material must never be committed to version control repositories.
2. Utilize the environmental variable mechanism within the MCP configuration file exclusively.
3. Establish a regular cadence for invalidating and refreshing API secrets.
4. Enforce stringent access permissions on the configuration file itself.

Project Setup Utilities

To prepare the execution environment: bash npm install

To compile the source files into deployable assets: bash npm run build

For development workflows incorporating automatic recompilation upon file changes: bash npm run watch

Operational Demonstrations

1. Querying Application Metadata: typescript invoke_mcp_utility({ endpoint_identifier: "glide-api", procedure_name: "get_app", parameters: { appId: "target-application-identifier" } });

2. Inserting a Record into a Data Structure: typescript invoke_mcp_utility({ endpoint_identifier: "glide-api", procedure_name: "add_table_row", parameters: { appId: "target-application-identifier", tableId: "target-schema-identifier", values: { field_a: "information_set_one", field_b: "information_set_two" } } });