singleops-mcp-server
Related Servers
Alternatives to singleops-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to manage Google Ads accounts through guarded tools for GAQL reporting, keywords, ads, budgets, callouts, and sitelinks, with dry runs and paused-by-default creates.Apache 2.0

ForIT MCP Gatewayofficial
AlicenseNot gradedqualityBmaintenanceEnables turning selected OpenAPI operations into authenticated MCP tools with branded OAuth, operation allowlisting, and live schema refreshes.Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to call the app's REST endpoints as tools for listing, retrieving, and creating items, plus health checks, over Streamable HTTP. Destructive delete operations are excluded by default.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect operational status and channels, lint human-reviewed plans, search and query ledger data, and run queue-based writes with dry-run defaults and safeguards against unverified or unapproved campaigns.MIT
- AlicenseNot gradedqualityCmaintenanceExposes standard MCP tools for secure calculation, knowledge-base retrieval, document statistics, and sensitive operations like email, export, and deletion with human-in-the-loop approval.MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to search and describe API routes, retrieve people, admissions, academics, and billing records, download exports, and optionally make changes against a school information system, read-only by default.6MIT
TDQS
Scored across 87 tools
Many tools overlap heavily: search_invoices, search_invoices_2, and search_invoices_archived_invoices target near-identical invoice table queries, and list_operations vs read_lead_list_operations both hit /api/v1/operations. There are also multiple parallel fullcalendar/timesheet list tools whose boundaries are unclear, plus a generic call_route that can reach anything, making tool selection ambiguous.
The singleops_read_<verb>_<resource> pattern is broadly applied, but verbs mix list_/get_/search_ for essentially the same operation and some names are awkward duplicates (list_timesheet_events_list, list_timesheets_list, search_invoices_2). It is readable but not reliably predictable.
87 tools is far beyond a well-scoped surface; many are mechanical one-per-endpoint dumps of the web app's internal traffic. This volume invites selection errors and could be collapsed via call_route or grouping.
The surface is almost entirely read-only listing/reporting; there are no create/update/delete tools for clients, jobs, visits, invoices, or tasks, so an agent cannot perform lifecycle operations without the generic call_route escape hatch. Read coverage is broad, but the actionable surface is thin.