A
licenseA
qualityD
maintenanceEnables interaction with Productive.io for task management, time tracking, budget monitoring, and project overview through natural language.
83
20 npm
ISC
Productive.io MCP Server
Related Servers
Alternatives to Productive.io MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Productive.io task management platform, allowing users to retrieve tasks and filter by assignee, status, or project.26 npmISC
- AlicenseCqualityDmaintenanceProvides complete integration with the Everhour API for time tracking, project and task management, enabling AI assistants to manage productivity workflows.4140 npm4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Clockify time tracking API to manage time entries, projects, tasks, and workspaces through natural language commands.34 npm5ISC
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with EverHour's API for time tracking, project management, task management, expense tracking, and reporting.-
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to the TrackingTime API v4 for managing projects, tasks, and team assignments. Users can start or stop timers, log manual time entries, and organize project workflows using natural language.2 npmMIT
TDQS
B3.3/5.0
Scored across 33 tools
Disambiguation4/5
Most tools target distinct resources and actions (e.g., get_task vs list_tasks, log_time vs list_time_entries). However, the three invoice-creation tools (create_invoice, create_invoice_from_previous, create_invoice_like_last_for_client) overlap in purpose and could be confused, though descriptions differentiate them.
Naming Consistency5/5
All tools use the productive_ prefix followed by a consistent snake_case verb_noun pattern (list_projects, get_task, create_invoice, update_line_item, delete_line_item). No mixing of camelCase or inconsistent verb styles.
Tool Count2/5
33 tools is heavy for a single server. While the broad domain (projects, tasks, time, invoices, budgets, etc.) might justify many tools, the count exceeds the typical 3-15 range and includes several granular read-only reference tools (document_types, subsidiaries, tax_rates) that contribute to bloat.
Completeness2/5
Coverage is heavily read-oriented. Many core resources lack full CRUD: no delete for projects, tasks, time entries, companies, people, deals, or bookings; no update for time entries, bookings, services, deals, people, or companies. Common workflows (e.g., updating a company, creating a deal) will fail.
Maintenance
ActivityInactive
ResponsivenessNo issues