Skip to main content
Glama
iniyusril

Dataverse Support MCP

by iniyusril
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Dataverse Support MCP

No user-submitted related servers found.

    Related Servers

    • lenovmail

      satuapps
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to securely read, search, and send email across IMAP and Microsoft Graph accounts, with scoped tokens, approval flows, and an audit trail.
      1
      MIT

    • support-inbox-mcp

      r28ai
      A
      license
      B
      quality
      B
      maintenance
      Enables agents to run support workflows across Gmail, Linear, Stripe, Slack, Notion and other apps — turning support email into tracked bugs with drafted replies, handling refunds end to end, and replying in-thread once issues are fixed.
      32
      Apache 2.0

    • Gmail MCP Server

      TechVest-Global
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered email management through Gmail, including search, send, drafts, labels, and an intelligent agent with human approval workflow and optional customer database integration.
      -
    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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool maps to a distinct step in the email-triage workflow: listing, reading, contact lookup/creation, knowledge search, replying, escalating, and closing without reply. The three terminal actions (create_reply, escalate_to_human, mark_processed) could overlap conceptually, but their descriptions clearly delineate when each applies. No two tools appear to do the same thing.

    Naming Consistency5/5

    All eight tools use snake_case with a leading verb (list_new_emails, get_email, find_contact, create_contact, search_knowledge, create_reply, escalate_to_human, mark_processed). The pattern is predictable enough that an agent can infer the verb-first convention throughout, with only trivial variation in the trailing noun form.

    Tool Count5/5

    Eight tools is a tight, well-scoped surface for an email support workflow; every tool covers a necessary step (read, research, respond, escalate, close). Nothing looks redundant or bolted on.

    Completeness4/5

    Core lifecycle is covered end-to-end: ingest, read, contact resolution, grounded answer lookup, draft/send reply, escalation to a Case, and silent close. Minor gaps exist—no way to list or inspect existing cases/drafts, no update_contact, and no attachment handling—but agents can work around these within the stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources