-
security-
license-
qualityEnables type-safe, bidirectional communication with Model Context Protocol services, allowing centralized management of model contexts over HTTP.
Last updated -
199
MIT License
The Glide API MCP Server enables secure, type-safe interaction with Glide API (v1 & v2) for app data management:
Configure API version and authentication using
set_api_versionor environment variablesRetrieve app information with
get_appList app tables using
get_tablesGet table rows with pagination support via
get_table_rowsAdd new rows to tables using
add_table_rowUpdate existing rows with
update_table_row
Provides a comprehensive interface to the Glide API (v1 & v2), allowing management of Glide apps, tables, and data with tools for retrieving app information, listing tables, fetching table data, adding new rows, and updating existing rows.
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 authenticationget_app: Get app informationget_tables: List app tablesget_table_rows: Get table dataadd_table_row: Add new rowupdate_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
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
Get app information:
use_mcp_tool({
server_name: "glide-api",
tool_name: "get_app",
arguments: {
appId: "your-app-id"
}
});
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"
}
}
});
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Facilitates secure and type-safe interactions with both v1 and v2 of the Glide API, allowing users to manage app data and perform CRUD operations on tables via a Model Context Protocol interface.
Related Resources
Related MCP Servers
- Asecurity-licenseAqualityA server for integrating with Placid.app's API, enabling listing templates and generating creatives using the Model Context Protocol with secure API token management.Last updated -914MIT License
- Asecurity-licenseAqualityProvides a Model Context Protocol interface for accessing Linear's issue tracking system, enabling users to query and search issues with TypeScript type safety and robust error handling.Last updated -1,45430MIT License
- -security-license-qualityEnables interaction with the Audius music platform API, supporting user, track, and playlist operations through the Model Context Protocol.Last updated -3