Software Engineer

PDQ launches MCP server to bring secure AI workflows to Endpoint Management. August 12, 2026 New integration lets IT teams investigate issues, answer operational questions, trigger deployments, and build custom automations from supported AI tools. SALT LAKE CITY, Utah - PDQ, a leading provider of endpoint management solutions, today announced early access to its Model Context Protocol (MCP) server, giving IT teams a new way to investigate their environments, answer questions, trigger deployments, generate reports, and build custom automations directly from supported AI tools including Claude, Microsoft Copilot, VS Code, and other MCP-compatible tools. PDQ's MCP server is being published through native AI connector directories, making it easier for customers to discover and securely connect to PDQ from the AI tools they already use to automate routine tasks. For example, an IT administrator could ask an AI assistant to: * Show every device missing Google Chrome. * Identify devices that have not checked in during the last 30 days. * Deploy the latest Chrome update to the marketing device group. * Create a Patch Tuesday interactive HTML report. * Report how many devices are still running Windows 10. * Identify devices missing Zoom and deploy it. "IT teams shouldn't have to spend their time translating a straightforward goal into the right combination of clicks, filters, and reports," said Mark Littlefield, VP of Product at PDQ. "PDQ's MCP server gives admins a more flexible way to investigate their environments and take action while keeping permissions, authentication, and auditing firmly under their control." Another Way to Work With PDQ PDQ's MCP server gives IT teams another way to interact with their endpoint environment. Because MCP exposes approved PDQ capabilities through customers' preferred AI tools, teams can investigate their environment, trigger deployments, generate reports, and build automations without changing the way they work. AI Access With Administrator-Defined Controls PDQ designed its MCP implementation to pair expanded automation capabilities with clear security boundaries. Connections use existing administrator-defined user permissions carry through to MCP interactions. Administrators determine what each user and AI integration can access and do, including whether they have read-only, reporting, deployment, or administrative permissions. Supported actions are authenticated and recorded in PDQ's audit log, including the user and AI client that initiated the request. Administrators can also view active MCP connections and revoke access from the app connections page in PDQ settings. The PDQ MCP server is available for free in early access to customers across all PDQ subscription tiers. Additional availability and packaging information will be announced at a later date. Claude users can access PDQ's MCP through Anthropic's Connectors Directory, with support for additional AI marketplaces planned. To learn more about how to customize and automate IT with PDQ AI, visit www.pdq.com/pdq-connect/features/ai-package-assistant/ Frequently asked questions. What is Model Context Protocol? Model Context Protocol, or MCP, is an open standard that allows AI assistants to securely interact with software. Instead of requiring a separate custom integration between every AI assistant and every software product, MCP provides a consistent way for software to make approved information and actions available to AI tools. What can IT teams do with PDQ's MCP server? IT teams can use supported AI assistants to investigate endpoint health, identify devices missing software, review deployment results, generate reports, answer operational questions, initiate deployments, and build custom automations. The actions available to each user depend on the permissions assigned by their PDQ administrator. Does MCP replace the PDQ interface? No. The PDQ interface remains available for managing devices, deployments, vulnerabilities, software, and other endpoint operations. MCP provides another way to interact with PDQ, particularly when an administrator wants to ask a question, investigate an issue, or incorporate endpoint management into a broader AI-assisted workflow. How does PDQ secure AI integrations? PDQ uses OAuth authentication, administrator-defined permissions, and audit logging to control MCP access. Existing PDQ permissions determine what a user can view or do through an AI assistant. Supported actions are attributed to the specific user and AI client that initiated them. Administrators can review active connections and revoke access from PDQ settings. How is MCP different from an API? APIs are primarily designed for developers who know which endpoint to call, what information to request, and how to structure the interaction. MCP makes product capabilities easier for AI assistants to discover and use based on the user's stated goal. In simple terms, APIs allow software to communicate with software. MCP gives AI assistants a standardized way to understand and interact with approved software capabilities. Many MCP servers are built using existing APIs. Is PDQ's MCP server officially supported? Yes. PDQ's MCP server is developed and supported by PDQ. It is not a community-maintained or unofficial integration. Who can access the MCP server? The MCP server is available to customers on all PDQ subscription tiers during early access. Access remains subject to administrator-defined permissions and supported AI clients. Availability and packaging after the early-access period will be announced separately. PDQ builds IT management tools that are simple, secure, and pretty damn quick. Trusted by system administrators, MSPs, and IT professionals worldwide, PDQ is an autonomous endpoint management solution for Windows and macOS devices, supporting patching, software deployment, and vulnerability management. Founded in 2001 and based in Salt Lake City, Utah, PDQ serves over 33,000 customers and has received G2 Leader and High Performer awards across Endpoint Management, Patch Management, and Remote Support. Learn more at pdq.com.

PDQ expands endpoint management and vulnerability capabilities. PDQ has introduced new capabilities that help IT teams resolve support issues more quickly, strengthen vulnerability management across Windows and macOS devices, and integrate endpoint data with existing enterprise systems. The release includes new ticketing integrations, macOS vulnerability management, and expanded APIs that unify support, security, and endpoint management workflows. New ticketing integrations with Zendesk, ServiceNow, and Halo bring device information and common endpoint actions directly into the ticket, expanding PDQ's existing integrations with Jira, Freshservice, and Freshdesk. The release also extends PDQ's vulnerability management workflow to macOS and introduces APIs for custom fields, vulnerability data, and deployment statuses. Together, the updates reduce the time technicians spend looking up devices, switching between tools, and moving information manually across support, security, and endpoint management workflows. The latest updates let sysadmins: * See a ticket requester's device details without leaving the ticket * From the ticket, deploy software, open a device in PDQ, or launch remote access * View and prioritize vulnerabilities across Windows and macOS devices from one interface * Remediate supported third-party application vulnerabilities across both operating systems * Bring PDQ assets, vulnerability, and deployment data into external systems and automated workflows * Streamline vulnerability reporting and administration with bulk actions and group-scoped reports * Customize your view of PDQ's visual dashboard with adjustable lookback times * Gain additional macOS process visibility "IT teams lose valuable time when the information they need is spread across ticketing, endpoint management, and security tools," said Mark Littlefield, VP of Product at PDQ. "These updates bring device context and action closer to where work is already happening, while giving teams a more consistent way to manage vulnerabilities across Windows and macOS." Resolve tickets without leaving the ticket. PDQ is expanding its ticketing integrations with new support for Zendesk, ServiceNow, and Halo. These additions join existing integrations with Jira, Freshservice, and Freshdesk, giving more technicians access to PDQ device information and actions directly inside the tools they already use. Authorized technicians can then: * Deploy any package available to them in PDQ * Open the device's details in PDQ * Launch a remote desktop session By reducing manual device lookups and tool switching, the integrations help technicians avoid targeting errors, resolve tickets faster, and maintain service-level performance. Ticketing integrations are available to PDQ Premium customers. macOS vulnerability management. PDQ now extends its existing vulnerability management workflow to macOS devices, giving IT teams one place to identify and prioritize risk across their Windows and Mac fleets. Vulnerability views now include devices running both operating systems, and CVE details indicate whether a vulnerability affects Windows, macOS, or both. Admins can investigate vulnerable software, review affected devices, and deploy available fixes using the same workflows they already use for Windows. When a supported macOS Package Library package is available, teams can use PDQ's remediation recommendations and deployment workflows to address vulnerable third-party applications. A single deployment can remediate supported applications across both Windows and macOS devices. Existing vulnerability management capabilities, including automation, role-based access controls, audit logs, and reporting, also apply to macOS devices. This gives IT teams one consistent way to manage devices, understand risk, coordinate remediation, and track activity across mixed operating system environments without context switching. New APIs for connected IT workflows. PDQ's new APIs provide deeper access to the data that supports everyday IT operations. Premium customers can now manage custom fields through the API, retrieve vulnerability data, and access deployment results and statuses programmatically. The Custom Fields API allows external systems to update or retrieve device metadata stored in PDQ. Teams can use it to synchronize information such as device ownership, business context, email addresses, or asset data from configuration management databases, asset management platforms, directories, and internal systems. The Vulnerabilities API lets teams bring vulnerability data into reporting, ticketing, compliance, security, and automation workflows. This can help organizations incorporate endpoint risk into broader operational and remediation processes without relying on repeated manual exports. The Deployment Status API gives external systems access to deployment results, including success and failure information. Teams can use this data to track outcomes, create reports, and trigger follow-up actions when deployments require attention. All three APIs will also be available through PDQ's Zapier integration, giving teams additional ways to build workflows without developing integrations from scratch. Additional platform updates. The release also includes several updates designed to make common endpoint management, vulnerability management, and remote support workflows more efficient: * macOS Processes tab: Admins can view running processes on individual Mac devices directly in PDQ. * Bulk vulnerability ignoring: Teams can ignore multiple vulnerabilities at once instead of updating each vulnerability individually. * Group-scoped vulnerability reports: Admins can limit vulnerability reports to selected device groups, making it easier to share relevant findings with specific teams, departments, customers, or business units. * Customizable lookback window: Teams can adjust the timeframe used to review. * CSV group creation: Admins can create device groups using CSV data, reducing the effort required to organize large sets of devices. Together, these updates expand PDQ's support for mixed Windows and macOS environments while helping IT teams connect vulnerability management, deployment, support, and reporting workflows.