Skip to main content
Glama
Sign In
Paperclip MCP server

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

    • Freshdesk MCP Server

      MSPbotsAIFramework
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and read tickets and their conversations, contacts, companies, agents, groups, knowledge base articles, SLA policies, business hours and canned responses, and, on explicit request, create and update records, reply to tickets, add notes, and perform confirmed deletes, merges or conversions. It is stateless and multi-tenant, taking per-request credentials via HTTP headers so every action is performed as the designated agent.
      Apache 2.0

    • DocsMint MCP Server

      quynhfurukawa4400
      F
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents access to a persistent document workspace so they can search, read, and update knowledge through 22 focused tools, 2 prompts, and 3 resources, with batch actions and direct workspace-item inspection. Runs either as a hosted Streamable HTTP endpoint with OAuth or API keys, or as a self-hosted stdio bridge pointed at your own instance.
      -

    • docket

      youssefaltai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to create and update issues, post comments, and manage docs in a self-hosted issue tracker, with changes visible live in the web UI.
      23 npm
      2
      MIT
    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/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

    ActivitySlowing
    ResponsivenessSyncing

    Resources