Brivo Velocity
Related Servers
Alternatives to Brivo Velocity
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets MCP clients such as Claude and ChatGPT read a rota and time-and-attendance account, exposing venues, groups, shifts, absences and absence types, time entries, venue events and staff names through read-only tools that never return pay data.MIT
- AlicenseBqualityBmaintenanceEnables Claude, Cursor, and other MCP clients to query PeopleForce HRIS data (employees, time-off, recruitment) via 27 read-only tools.284MIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to Workday HCM data such as workers, organizations, locations, job profiles, and cost centers through MCP tools an LLM can call.-
- FlicenseAqualityCmaintenanceRead-only MCP server that connects Claude Desktop to the publisher-side Ad Manager API so users can browse networks, saved reports, orders, and line items, and run saved reports to pull their rows into a conversation. No tool mutates data, and per-user OAuth ensures each person inherits only their existing account permissions.5-
- AlicenseAqualityBmaintenanceEnables Claude or any MCP client to read live and historical Sunsynk inverter, battery, and solar data, plus inverter settings, through the Sunsynk Connect cloud API. It is read-only and lets users ask natural-language questions about generation, consumption, charging, and configuration.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT, Copilot, and Cursor to read Google Ads data—campaigns, ad groups, ads, keywords, search terms, budgets, conversion actions, change history, and custom GAQL queries—through 17 read-only MCP tools. It supports OAuth-authenticated access to real accounts without requiring a developer token, keeping all operations read-only and auditable.27 npmAGPL 3.0
TDQS
Scored across 75 tools
Many tools are scope-variant listings of the same underlying resources (e.g., List_sites/List_root_sites/List_sites_proximity, List_access_points/List_site_access_points, List_cameras/List_site_cameras/List_access_point_cameras). Descriptions clarify intent, but the 75-tool set still creates real misselection risk among similar list/get endpoints.
Almost all tools follow a predictable List_/Get_/Count_ + snake_case noun pattern, which is easy to parse. There are minor anomalies such as Get_admin_assignments and the generic List_activities, but the convention is largely consistent.
75 tools is an extreme count for an MCP surface, especially because many are granular read-only list/get endpoints that could be consolidated with filters or pagination. This far exceeds the typical 3-15 well-scoped range and creates a heavy cognitive load.
The surface appears entirely read-only (List, Get, Count); there are no create, update, delete, assign, lock/unlock, or other lifecycle operations. For an access-control domain, this leaves severe gaps in managing users, credentials, groups, sites, and access points.