Skip to main content
Glama
Dataverse Support MCP

Dataverse Support MCP

by iniyusril

Related Servers

Alternatives to Dataverse Support MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables users to triage logistics, supply-chain, and commerce email, extract attachment text, fill highlighted DOCX/XLSX templates, search a knowledge folder, and draft replies, with sending gated behind explicit confirmation. It can also connect to a SaaS workspace where sending creates an approval request.
      11
      -
    • A
      license
      Not graded
      quality
      B
      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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables an LLM agent to work a FreeScout support inbox without an API key, authenticating through the normal web UI with a pasted browser session cookie or FreeScout username and password. It lets agents read and search conversations, pull ticket and satisfaction reports, add internal notes, save reply drafts, manage tags, close tickets, and optionally forward to an operator allow-list — all under the agent's own mailbox permissions, and never emailing customers.
      1
      MIT

    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 recent community issues