The Glide API MCP Server provides a Model Context Protocol interface for interacting with the Glide API (both v1 and v2 versions), allowing you to easily manage Glide apps, tables, and data using standardized MCP tools.
The recommended way to configure the server is through environment variables in your 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 securely stores your API credentials outside of your code and keeps them out of version control.
You can also set or override API settings 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 that runtime configuration will override environment variables for the current session.
The server provides several tools for interacting with Glide apps:
To retrieve information about a Glide app:
use_mcp_tool({
server_name: "glide-api",
tool_name: "get_app",
arguments: {
appId: "your-app-id"
}
});
To get a list of tables in your app:
use_mcp_tool({
server_name: "glide-api",
tool_name: "get_tables",
arguments: {
appId: "your-app-id"
}
});
To fetch rows from a specific table:
use_mcp_tool({
server_name: "glide-api",
tool_name: "get_table_rows",
arguments: {
appId: "your-app-id",
tableId: "your-table-id"
}
});
To add a new 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"
}
}
});
To update an existing row in a table:
use_mcp_tool({
server_name: "glide-api",
tool_name: "update_table_row",
arguments: {
appId: "your-app-id",
tableId: "your-table-id",
rowId: "row-id-to-update",
values: {
column1: "updated-value",
column2: "another-updated-value"
}
}
});
When using this MCP server, follow these security guidelines:
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "glide-api" '{"command":"node","args":["path/to/build/index.js"],"env":{"GLIDE_API_KEY":"your-api-key-here","GLIDE_API_VERSION":"v2"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"glide-api": {
"command": "node",
"args": [
"path/to/build/index.js"
],
"env": {
"GLIDE_API_KEY": "your-api-key-here",
"GLIDE_API_VERSION": "v2"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"glide-api": {
"command": "node",
"args": [
"path/to/build/index.js"
],
"env": {
"GLIDE_API_KEY": "your-api-key-here",
"GLIDE_API_VERSION": "v2"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect