A Model Context Protocol server for interacting with the Glide API (v1 & v2).
- Support for both Glide API v1 and v2
- Secure API key handling through environment variables
- Type-safe TypeScript implementation
- Comprehensive error handling
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
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
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.
- 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
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run watch
- 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"
}
}
});