Skip to main content
Glama
auralab-dev

Paperclip MCP server

by auralab-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Paperclip MCP server

No user-submitted related servers found.

    Related Servers

    • project-tasks-mcp

      augustoOliveira1993
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables managing projects, features, tasks, dependencies, executions, and human review through a Streamable HTTP endpoint, along with persistent inter-agent cooperation via task messaging and event subscriptions. It also supports administrative actions such as approvals, cancellations, unblocking, and member management.
      -

    • AutomateHub

      Xesderte
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate GitHub repository management, issue tracking, and commits using natural language.
      3 npm
      Apache 2.0

    • Overdrive MCP Server

      lfnovo
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely access and manage CRM pipeline, relationships, tasks, notes, files, and deal context through authenticated Streamable HTTP/OAuth, inheriting the signed-in user's permissions and business-unit isolation.
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, with clear singular/plural pairs such as issue/issues and document/documents. The main ambiguity is paperclip_context vs paperclip_heartbeat_context, but their descriptions differentiate current run/wake state from an issue-specific heartbeat.

    Naming Consistency5/5

    All tools share the paperclip_ prefix and follow a predictable pattern: read operations use resource nouns while mutations use resource_action naming like paperclip_issue_create and paperclip_comment_add. The paperclip_raw fallback is clearly labeled and does not disrupt the overall convention.

    Tool Count4/5

    At 16 tools the surface is slightly above the ideal 3-15 range, but the count is justified by the domain: issue lifecycle, comments, documents, agent lookup, context retrieval, and a raw fallback each have a distinct purpose. Nothing feels redundant or excessive.

    Completeness4/5

    The core issue workflow is well covered: list/get/create/update/checkout/release, plus comments, documents, agents, and context. Minor gaps such as no explicit delete or comment edit exist, but the update operations and paperclip_raw fallback give agents practical workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources