By adding a Right Click Tools MCP Server, you can run RCT actions as requests to your AI tools.
Currently, you can set up a Right Click Tools integration within Visual Studio Code and GitHub Copilot CLI.
The Right Click Tools MCP Server is available to both RCT Enterprise customers and Community users. Enterprise customers will typically be able to run 75+ Right Click Tools actions, while Community users can access a subset of about 30 actions. See the full list of available actions.
Minimum Right Click Tools Version: 5.12.2608
NOTE: Right Click Tools Enterprise licenses are not subject to rate limiting. Community licenses are limited to 10 requests every 15 minutes.
Add the Right Click Tools MCP Server
To add the Right Click Tools MCP Server in VS Code:
1. Open VS Code and sign into GitHub Copilot.
2. Press F1 to open the Command Palette.
3. In the search bar, enter something like 'add mcp server' and select the MCP: Add Server command.
4. As the type of MCP Server to add, choose Command (stdio).
5. Enter the path to Recast.RightClickTools.Service.exe:
"C:\Program Files (x86)\Recast Software\Recast Console Extension\Recast.RightClickTools.Service\Recast.RightClickTools.Service.exe" mcp
6. Enter a descriptive name, such as RecastRightClickToolsService.
VS Code will open your user profile mcp.json with a configuration similar to the following:
{"servers": {"RecastRightClickToolsMcp": {"type": "stdio","command": "C:\\Program Files (x86)\\RecastSoftware\\Recast Console Extension\\Recast.RightClickTools.Service\\Recast.RightClickTools.Service.exe","args": ["mcp"]}},"inputs": []}
7. Start the MCP server by clicking Start above the server details.
Startup can take up to 30 seconds while the tools load. If needed, you can select More > Show Output to review the log.
The number of available tools depends on your Right Click Tools permissions, licensing, and configuration.
Most RCT Enterprise users with full permissions will see 75+ tools, while RCT Community users typically see 30+.
View/Manage Right Click Tools via the MCP Server
To view or manage tools:
1. Open the chat panel and select the Configure tools button (the sliders icon).
The Configure Tools panel that opens displays all MCP servers available in the session, along with which ones are enabled and which tools they expose.
When running MCP actions over a Recast Agent route, the device name in your MCP server request must match the device name that displays on the Recast Agents page in your Recast Management Server. Matching is case-sensitive. We strongly recommend entering all device names in upper case lettering, or creating a skill or instructions file for upper case device names.
Check That Your MCP Server is Enabled
To verify that your RCT MCP server is enabled:
1. Click the gear icon to the right of the MCP server name to open mcp.json and confirm the configuration.
2. Run the sample prompt:
‘Can you check if Dev1-pc-05 is pingable and then get the list of bitlocker status of the device?’
You should see the tool name appear in light gray while Copilot is working. If the inputs look safe, approve the tool run.
Enable Autopilot Approvals (Optional)
If you want fewer approval prompts, you can enable Autopilot approvals, but do so with caution.
To enable Autopilot approvals:
1. In mcp.json, click Default Approvals.
2. Select Autopilot (Preview).
Add the Right Click Tools MCP Server
Before attempting to add the MCP Server, make sure Copilot CLI is installed and that you are signed in with your GitHub account.
To add the Right Click Tools MCP Server in Copilot CLI:
1. Open PowerShell or Command Prompt and run copilot to start Copilot CLI.
2. Sign in, if prompted.
3. Run /mcp add RecastRightClickToolsService.
4. As the Server Type, choose 'STDIO'.
5. Enter the server command:
"C:\Program Files (x86)\Recast Software\Recast Console Extension\Recast.RightClickTools.Service\Recast.RightClickTools.Service.exe" mcp
Check That Your MCP Server is Enabled
To verify that your RCT MCP server is enabled, try running a sample prompt:
‘Can you check if Dev1-pc-05 is pingable and then get the list of bitlocker status of the device?’
When running MCP actions over a Recast Agent route, the device name in your MCP server request must match the device name that displays on the Recast Agents page in your Recast Management Server. Matching is case-sensitive. We strongly recommend entering all device names in upper case lettering, or creating a skill or instructions file for upper case device names.
The number of Right Click Tools actions available to you through the MCP server will depend on your Right Click Tools licensing, permissions, and configuration.
Most Right Click Tools Enterprise customers with full permissions will see all plugin actions, while RCT Community users typically have access to around 30 tools.
Full list of actions available via the RCT MCP server:
- Administration_GetServerVersion
- Administration_GetExecutionHistory
- Administration_ListProxies
- Administration_ListAgents
- Administration_ListAgentGatewaysWithAgents
- Administration_ListMemcmServiceConnections
- Administration_ListActiveDirectoryServiceConnections
- Administration_ListAzureActiveDirectoryServiceConnections
- Administration_ListMbamServiceConnections
- ActiveDirectory_GetADComputersInGroup
- ActiveDirectory_GetADUser
- ActiveDirectory_GetADComputer
- ActiveDirectory_GetADComputerWithLAPSData
- ActiveDirectory_GetADGroup
- ActiveDirectory_SearchADGroups
- ActiveDirectory_SearchADComputers
- ActiveDirectory_SearchADUsers
- ActiveDirectory_IsAccountEnabled
- ActiveDirectory_UnlockAccount
- ActiveDirectory_GetAccountGroupMembership
- ActiveDirectory_GetGroupMembers
- ActiveDirectory_GetBitLockerRecoveryData
- ConfigMgrServer_GetWarrantyInformation
- ConfigMgrServer_GetComputerWarranty
- ConfigMgrServer_GetComputerWarrantyByComputerName
- ConfigMgrServer_GetRecentDevicesScanned
- ConfigMgrServer_GetDeviceCount
- ConfigMgrServer_GetManufacturerCounts
- ConfigMgrServer_GetDevicesWithWarrantyExpiringSoon
- ConfigMgrServer_GetCollectionsforDevice
- ConfigMgrServer_GetCollectionVariablesforDevice
- ConfigMgrServer_ContentDetails
- ConfigMgrServer_GetAllDeviceCollections
- ConfigMgrServer_GetAllCollections
- ConfigMgrServer_GetAllUserCollections
- ConfigMgrServer_GetCollectionsforUser
- ConfigMgrServer_GetContentStatus
- ConfigMgrServer_GetDeviceCollectionFolders
- ConfigMgrServer_GetDeviceCollectionInformationforDevice
- ConfigMgrServer_GetDeviceCollectionMembers
- ConfigMgrServer_GetDistributionPointStatusforPackage
- ConfigMgrServer_GetDistributionPointGroupStatusforPackage
- ConfigMgrServer_GetBoundaries
- ConfigMgrServer_GetBoundaryGroups
- MBAM_GetRecoveryKeysForDevice
- MBAM_GetTPMHash
- MBAM_GetTPMHashForUser
- MBAM_GetMBAMCompliance
- MBAM_GetMBAMComplianceForAllMachines
- MBAM_GetMachinesWithMBAMKeys
- MBAM_GetMachinesWithMBAMKeys_v2
- Registry_GetValue
- Registry_ListValues
- Registry_ListSubkeys
- Registry_ListHives
- ConfigMgrClient_RunClientAction
- ConfigMgrClient_DeployedApplications
- ConfigMgrClient_GetUserPolicyEndpoint
- ConfigMgrClient_GetDeviceId
- ConfigMgrClient_GetDeployedPrograms
- ConfigMgrClient_GetServiceWindows
- ConfigMgrClient_GetConfigurationBaselines
- ConfigMgrClient_GetDeployedTaskSequences
- ConfigMgrClient_TaskSequenceInformation
- ConfigMgrClient_PackageInformation
- ConfigMgrClient_MissingSoftwareUpdates
- BitLocker_GetBitLockerStatus
- BitLocker_GetRecoveryPasswordFromDevice
- Network_PingComputer
- SystemInformation_GetAllLocalGroupMembers
- SystemInformation_GetRunningProcesses
- SystemInformation_GetBatteryInformation
- SystemInformation_GetLoggedInUsers
- SystemInformation_GetUserSessions
- WindowsSecurity_GetTpmStatus
- WindowsSecurity_GetWindowsFirewallProfiles
- WindowsSecurity_GetWindowsFirewallRules
