"browser tool" matching MCP servers:

Provides MSP support tools (ticket search, draft response, KB search, update) with a deterministic security guardrail that refuses to draft responses for security tickets based on content scanning, even if mislabeled.

Provides ServiceNow ITSM tools (incidents, knowledge, CMDB, user lookups) to AI agents, with an evaluation harness that measures tool-selection accuracy, task completion, and latency.

MCP server that authenticates via browser session cookies to access Zendesk's REST API without API tokens, supporting reads and writes with agent permissions.

A prompt-injection-aware MCP server demonstrating guardrails for agentic tool use, including permission tiers, untrusted-content quarantine, and heuristic injection detection, with a fictional ticket-triage assistant.

Enables Claude and other MCP clients to place, transfer, and hang up calls, review call history and dispositions, download recordings, inject single or bulk leads into lists and campaigns, and manage GoHighLevel sub-account services through the VoIPSense Cloud API. Includes a read-only mode and tool annotations so write actions are confirmed appropriately.

Enables AI assistants to send template-based SMS messages through EngageLab. Supports multiple recipients and template parameters via a single tool.

A Model Context Protocol (MCP) server that connects LLMs to the Zendesk Support & Help Center APIs — with per-user OAuth 2.1 PKCE authentication and fine-grained tool visibility controls.

Enables interaction with Pega case operations through a metadata-driven tool layer, allowing users to fetch, update, and manage cases. It supports standard Pega actions such as retrieving case details, attaching documents, and submitting case actions via API.

Provides customer lookup, transaction history, knowledge-base search, and ticket management tools to any MCP client.

Protects AI support tools with Descope JWT authentication and scope-based authorization, enabling secure customer support operations like refunds with granular access control.

Local-first MCP server for Quo/OpenPhone automation across messaging, calls, contacts, users, phone numbers, and webhooks via a clean stdio tool surface.

Enables assistants to read and modify contacts, conversations, messages, pipelines, tasks, inboxes, and AI agents through the CRM REST API, using separate read-only or read-write tool sets. Runs over local stdio or stateless Streamable HTTP with token-based scope separation.

MCP server providing 1:1 tool parity with Arcade.dev's HubSpot Conversations API toolkit, enabling reading and sending conversation messages, managing threads, inboxes, channels, and custom channels from any MCP client.

Exposes the Gapify (Chatwoot-compatible) customer-support API as MCP tools, letting assistants list and search conversations and contacts, send replies, assign teams, apply labels, and resolve tickets in English or Persian. Write actions carry annotations for client confirmation, and a raw-request tool covers endpoints outside the generated set.

MCP server to help manage a WHMCS installation.

A single MCP server that provides a provider-neutral 14-tool contract for telephony operations (calls, SMS, recordings, transcripts, and number lifecycle), supporting hosted, fully local, or bring-your-own-key backends.

CallHub MCP is a Python-based tool that allows you to interact with the CallHub API through Claude. This tool provides a comprehensive set of functions for managing contacts, phonebooks, agents, teams, campaigns, and other CallHub resources.

Enables secure support-ticket and customer-account operations with signed JWT authentication, prompt-injection and tool-poisoning guardrails, and human-in-the-loop confirmation for destructive actions.

A browser-accessible Model Context Protocol server that enables AI assistants to manage ServiceNow incidents using Server-Sent Events. It provides comprehensive tools for creating, listing, retrieving, and updating incidents through a type-safe RESTful interface.

Enables AI agents to create tickets, post public replies, add private internal notes, change ticket status, and list tickets across Zendesk, Freshdesk, and Help Scout using one consistent tool vocabulary and unified credential setup. It handles each platform's differing authentication schemes and field conventions, including Help Scout's non-refreshable OAuth2 client-credentials tokens.