mcp-office-suite
Related Servers
Alternatives to mcp-office-suite
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceA meta-MCP server that aggregates and proxies other MCP servers, letting LLMs search for, add, configure, enable, disable, and bundle backend servers at runtime. Tools from those servers are automatically exposed under unified prefixes, with persistent configuration, health checks, and support for stdio, HTTP, and hybrid transports.-
- AlicenseAqualityAmaintenanceMCP gateway/proxy: multiplexes tool calls across upstream MCP servers into one aggregated, namespaced catalog and logs every call. Local, single-user, $0/month by default.2MIT
- AlicenseNot gradedqualityAmaintenanceAggregates multiple MCP sub-servers into a single unified entry point, supporting stdio and Streamable HTTP protocols, with a web-based management interface for configuration, routing, and tool management.11 npm1MIT
- AlicenseBqualityBmaintenanceA flexible proxy server that aggregates multiple backend MCP servers into a single interface using STDIO or SSE transports. It supports dynamic server management via an HTTP API and utilizes namespacing to prevent tool conflicts across connected services.31MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for time tracking, project management, and AI-powered memory storage using semantic search. It enables users to log time, manage client billing, and capture shared or personal ideas through integrated tools and team collaboration features.1MIT
- FlicenseNot gradedqualityAmaintenanceAggregates multiple backend MCP servers (Stdio, SSE, and Streamable HTTP) and exposes their combined tools and resources through a single unified SSE or Streamable HTTP endpoint, or as a standalone Stdio server. It routes tool calls and resource requests to the right backend and offers optional web-based admin, authentication, and per-tool control.-
TDQS
Scored across 129 tools
Within each sub-domain tools are fairly distinct, but cross-domain collisions exist: 'report' (timesheet) vs report_list/report_get/report_page/report_export_csv (saved reports / duplicate checks), and invoice_business_set vs docx_business_set both write the same profile. Descriptions are unusually explicit in steering callers ('use X instead'), which rescues an otherwise confusing set, but the overlap remains real.
Conventions are mixed: noun_verb ordering (schedule_list, invoice_create, client_add) coexists with verb_noun (watch_add, clause_add, convert_many) and bare nouns/verbs (report, now, convert, conflicts, overlap, forecast). All snake_case, but the verb/noun ordering and the presence of bare names make the pattern unpredictable.
129 tools is far beyond any reasonable single-server surface, even granting it bundles many domains. Each sub-domain (time tracking, invoicing, schedules, sheets, price watches, FX, docx, resumes, timezone, PDF, calendar, duplicate checks) would be its own server, and the aggregate is unmanageable.
Coverage is genuinely deep: CRUD/lifecycle exists for clients, invoices, schedules, clauses, watches, sheets, PDFs, docs, calendars and reports, plus cross-linking tools (entry_mark_billed, event_to_time_entry, fx_rates_for). Only minor gaps and a few read-vs-write asymmetries, so it is close to complete for the sprawling scope.