Slide MCP Server
Related Servers
Alternatives to Slide MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides safe, read-only CRM access for AI assistants with per-key scopes, field masking, rate limits, and a full audit log of allowed and blocked actions.MIT
- AlicenseNot gradedqualityAmaintenanceEnables read-only file-management operations from AI assistants, including health checks, connection and folder listings, search, share-link resolution, metadata retrieval, and on-demand document reading.MIT
- FlicenseAqualityBmaintenanceProvides read-only visibility into CyberQP privileged access management data, including customer and account metadata, tenant event logs, and Just-In-Time account status and policies, for AI assistants.10-
- FlicenseAqualityBmaintenanceEnables read-only access to AlertOps incident alerting and on-call data, including alerts, users, groups, integrations, and schedules, for AI assistants.11-
- FlicenseNot gradedqualityDmaintenanceProvides read-only access to Velero backup and schedule resources in Kubernetes clusters, enabling AI agents to inspect backups, schedules, and generate Velero YAML manifests safely without write permissions.2-
- FlicenseBqualityDmaintenanceProvides read-only EspoCRM access for AI assistants, enabling record retrieval and preparation of signed change sets without direct modification or deletion.7-
TDQS
Scored across 43 tools
Each tool maps to a distinct entity or sub-resource—accounts, agents, backups, snapshots, restores, exports, networks, VLANs, billing, audit, users—so the boundaries are mostly clear. A few list/get pairs, especially around file restores, restores pushes, and image exports, could be confused at a glance, but the descriptions resolve the differences.
All tools follow a consistent slide_<verb>_<noun> pattern, with get_ for single resources and list_ for collections. The one semantic outlier, slide_search_agent_files, still uses a clear verb-first convention and fits the overall style.
43 tools is well above the 3-15 well-scoped range and even past the 16-25 heavy range. The count is inflated by exhaustive read-only views of many sub-resources, which feels bloated even if each individual tool is narrowly defined.
The read-side surface is broad, covering list/get/browse for nearly every entity, but there are zero create, update, delete, or action tools for backups, snapshots, restores, alerts, devices, billing, users, or networks. Any workflow requiring lifecycle management or triggering operations will dead-end.