Skip to main content
Glama
borgels

mcp-server-productive

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-productive

No user-submitted related servers found.

    Related Servers

    • productive-mcp-rb2

      rubenlangeweg
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Productive.io for task management, time tracking, budget monitoring, and project overview through natural language.
      83
      6 npm
      ISC

    • Productive Simple MCP

      druellan
      A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol (MCP) server for accessing Productive.io API endpoints (projects, tasks, comments, todos), tailored for read-only operations, providing streamlined access to essential data while minimizing token consumption
      18
      MIT

    • project-bridge

      adrianohsnegrao
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to read structured project context and propose task changes that require explicit human approval, with scoped permissions, idempotency, and a full audit trail.
      MIT

    • bokio-mcp

      diblaze
      F
      license
      B
      quality
      B
      maintenance
      Enables interaction with the Bokio accounting API for managing journal entries, invoices, customers, items, and more, with read-only mode by default for safety.
      18
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct operation: reading one record, listing, creating, updating, deleting, running a named action, staging/committing writes, tracking time, or performing a meta/introspection task. Even the closer pairs like get/list and describe_resource/describe_custom_fields are clearly separated by resource scope and purpose.

    Naming Consistency5/5

    All tools follow the snake_case productive_<verb> pattern, with most using verb_noun (productive_check_connection, productive_run_action) and a few using bare verbs (productive_get, productive_list). This is consistent and predictable, with no style mixing or vague duplicate verbs.

    Tool Count5/5

    Twelve tools is well within the ideal scope for a broad API integration server. The set covers generic CRUD, named actions, time tracking, staged writes, and meta/discovery tools without ballooning into redundant or overly granular endpoints.

    Completeness5/5

    The server provides full lifecycle coverage: read, list, create, update, delete, run actions, and commit staged operations, plus support for custom fields and resource contracts. The meta tools fill the gaps that typically cause agent failures, such as knowing resource-specific filters, writable attributes, and custom-field keying.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources