Skip to main content
Glama
bitterdev

pixelletter-mcp

by bitterdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to pixelletter-mcp

No user-submitted related servers found.

    Related Servers

    • agent-mail-mcp

      postalform
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that lets AI agents create reviewable physical mail drafts, validate quotes, and pay for postage via MPP or x402 protocols.
      2
      MIT

    • mailsnail

      iancollins27
      A
      license
      Not graded
      quality
      B
      maintenance
      An open-source MCP server for sending physical mail (letters, postcards, certified mail) directly from AI agents, with per-piece payment and no account signup needed.
      MIT

    • mailbox-mcp

      arbengine
      A
      license
      A
      quality
      D
      maintenance
      Official mailbox.bot MCP server for AI agents. Send letters, certified mail, postcards, and receive scanned inbound physical mail with sandbox keys, approval controls, tracking, and webhooks.
      29
      83 npm
      2
      MIT

    • pdf-letter-mcp

      bitterdev
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server that generates print-ready PDF letters with DIN 5008 compliant address positioning for window envelopes, handling structured content offline without external APIs.
      7
      30 npm
      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.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct action: sending a letter, sending a fax, checking account info, signing an invoice, and retrieving interface reference data. Even though send_letter and send_fax both handle document transmission, their descriptions clearly separate postal plus optional fax from fax-only sending.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: send_letter, send_fax, get_account_info, sign_invoice, get_interface_reference. The verbs clearly indicate the action and the nouns identify the resource or target, making the set predictable.

    Tool Count5/5

    Five tools is well-scoped for this server's purpose. Each tool covers a distinct capability without redundant utilities or an overwhelming surface area, making the tool set easy for an agent to navigate.

    Completeness4/5

    The core workflows are covered: sending letters, sending faxes, checking account balance, signing invoices, and accessing interface documentation. The main gap is a lack of order status or transaction lookup after sending, but this can be worked around since transaction IDs are returned.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources