A
licenseNot graded
qualityC
maintenanceEnables type-safe, bidirectional communication with Model Context Protocol services, allowing centralized management of model contexts over HTTP.
209
MIT
Glide API MCP Server
by knmurphy
Related Servers
Alternatives to Glide API MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA server for integrating with Placid.app's API, enabling listing templates and generating creatives using the Model Context Protocol with secure API token management.314 npm14MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to interact with Fastly's CDN API through the Model Context Protocol, allowing secure management of CDN services, caching, security settings, and performance monitoring without exposing API keys.213 npm7MIT
- FlicenseBqualityBmaintenanceEnables seamless integration with Typecast API through the Model Context Protocol, allowing clients to manage voices, convert text to speech, and play audio in a standardized way.113-
- AlicenseNot gradedqualityBmaintenanceEnables interaction with the Audius music platform API, supporting user, track, and playlist operations through the Model Context Protocol.7 npm5MIT
- AlicenseNot gradedqualityFmaintenanceProvides 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.210 npm30MIT
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.