Skip to main content
Glama
Sign In
Quolle MCP

Quolle MCP

by Quolle-main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Quolle MCP

No user-submitted related servers found.

    Related Servers

    • Lemon Email MCP Server

      manojk0303
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to send transactional emails programmatically through the Lemon Email API. Provides simple email sending capabilities with customizable sender information, recipients, and content.
      2
      MIT

    • agentisend

      fortuneflick
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.
      267 npm
      MIT
    • vaemail

      vaemailofficial

      vaemail
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send transactional email, authenticate sending domains, track delivery, and diagnose deliverability issues programmatically.
      13
      87 npm
      MIT

    • GetMailer MCP Server

      getplatform
      A
      license
      A
      quality
      D
      maintenance
      Enables sending transactional emails through GetMailer from AI assistants. Supports email operations, template management, domain verification, analytics, suppression lists, and batch email jobs.
      14
      18 npm
      MIT

    • Resend MCP Server

      jannikco
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect verified sending domains and submit transactional emails through hosted tool discovery, schema validation, and policy-governed execution using a single gateway API key.
      17,988 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 6 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action: sending (single vs. batch is clearly delimited by the 100-email, all-or-nothing description), lookup by id vs. listing, cancellation, and domain listing. No two tools could plausibly be chosen for the same intent.

    Naming Consistency5/5

    All six tools follow a strict verb_noun snake_case pattern (send_email, send_batch, get_email, list_emails, list_domains, cancel_email). Verb choices are standard CRUD-style and predictable.

    Tool Count5/5

    Six tools is well within the ideal 3-15 range and each earns its place in a transactional email workflow (send, batch send, cancel, inspect, list, validate sender domain). Nothing looks like padding or a leftover utility.

    Completeness3/5

    Core send/read/cancel flow is covered, but cancel_email implies scheduled sends exist while no tool lets an agent schedule one, and domain verification/creation and template discovery or management are absent even though send_email accepts template slugs. These are meaningful gaps an agent would hit in real workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources