Skip to main content
Glama

Related Servers

Alternatives to pingen-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables sending physical letters (including registered mail) from PDFs via the Pingen API, with tools to manage drafts, submit, track, and cancel letters.
      9
      18 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables creating professional documents (invoices, contracts, certificates, proposals, reports) via the DocuQueue API, with tools for template management, filling, previewing, and PDF generation.
      28 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables authenticated management of email, drafts, sending, domains, contacts, templates, campaigns, workflows, and webhooks through typed MCP tools backed by a REST API.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables access to all DocuSign product APIs through curated tools and raw API calls, with OAuth support for hosted MCP clients.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Enables sending transactional emails, managing templates, suppression lists, sending domains, webhooks, subaccounts, and retrieving account metrics via the SparkPost API.
      20
      356 npm
      MIT

    TDQS

    B3.1/5.0

    Scored across 49 tools

    Disambiguation4/5

    Each tool maps to a distinct REST endpoint and the resource prefix (letters, emails, ebills, batches, webhooks, organisations) plus action suffix usually makes selection clear. A few pairs need care — organisation-wide event feeds (organisations_letters_events_sent) versus per-letter events (letters_events), and files_file_upload which actually only fetches upload metadata rather than uploading anything.

    Naming Consistency3/5

    All names are snake_case and mostly follow a resource_action shape, but the verb vocabulary is inconsistent (list vs index, show vs get, delete vs destroy, edit vs update) and the ordering flips between resource-first (letters_list) and path-first (organisations_letters_events_delivered, files_file_upload). Readable, but not predictable enough for an agent to guess names.

    Tool Count2/5

    49 tools is well beyond a comfortable working set for an agent, even though it mirrors a real API surface of three delivery channels times roughly ten operations each. Much of the weight comes from repetitive per-channel variants (file, events, events_image, send, cancel) that could be consolidated.

    Completeness4/5

    CRUD plus lifecycle actions (send, cancel, file, events, statistics) are covered for letters, emails, ebills and batches, along with organisations, user, associations and webhooks. Minor gaps: no webhook update or webhook delivery/event listing, no letter or email edit operation, and no price calculator for channels other than letters.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data