mcp-office-suite
Related Servers
Alternatives to mcp-office-suite
No user-submitted related servers found.
Related Servers
- 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 gradedqualityBmaintenanceAggregates 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.41 npmMIT
- 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
- FlicenseNot 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.1-
- FlicenseNot gradedqualityCmaintenanceA remote MCP server for the Moxie Public API, deployable to Cloudflare Workers. Exposes all 29 documented Moxie endpoints as MCP tools for managing clients, contacts, projects, tasks, invoices, payments, and more.-
- FlicenseNot gradedqualityBmaintenanceMCP server that wraps the BIP work-hour reporting CLI into 11 tools, enabling automated timesheet preview, scanning, submission, and approval management. It keeps internal credentials and configuration server-side, supporting both streamable HTTP and stdio transports.-
TDQS
Scored across 117 tools
Many tool families are clearly described, but several pairs blur together: invoice_business_set and docx_business_set write the same shared profile, pdf_split and pdf_pages overlap for single ranges, and overlap/find_meeting_slots plus the rate_* family are easy to confuse. The detailed descriptions help, but with 117 tools an agent will still misselect.
Most tools follow a readable snake_case resource_action style (schedule_create, sheet_read, clause_update), but there are notable exceptions: convert, convert_many, convert_time, export_csv, and bare nouns like now, overlap, forecast, report, free_busy. The mix is still readable, so it is not chaotic.
117 tools is far beyond any reasonable single-server surface and dwarfs the extreme-mismatch threshold of 50+. This should be split into focused servers for documents, spreadsheets, PDFs, invoicing, calendar, time tracking, FX, and price tracking.
Each broad area has substantial coverage, but there are notable dead ends: invoice_list/get reference credit notes yet no tool creates them, proposals have create/update but no get/list, and contract_create returns a reference with no read/list/update/delete surface. Agents cannot complete those lifecycle workflos.