Silect Assistant FAQ

The Silect Assistant runs as a windows service on a non-dedicated Windows Server system. It requires access to a supported AI runtime and language model. There are many supported cloud AI runtimes including Microsoft Foundry and OpenAI as well as on-premises AI runtimes including Ollama and Foundry Local.  In many cases existing AI runtimes can be used. The Silect Assistant also requires access to SCOM.

Yes – the Silect Assistant is secure. It can be deployed fully on-premise so no data leaves your firewall. If you are using a cloud AI runtime like Microsoft Foundry, they do not store your data or share your data with anyone else. Also the Silect Assistant fully respects users roles as defined in SCOM and will not allow users to do anything that they aren’t already allowed to do in SCOM.

Yes. Because the Silect Assistant is built on the Model Context Protocol (MCP), it can interact with other systems including ServiceNow, JIRA, Grafana and virtually any other system that provides an MCP server. As a result the integration opportunities are virtually unlimited!

Yes. Silect Assistant includes both an MCP Client as well as an MCP Server to enable virtually any integration scenario using the Model Context Protocol.

Easy. Edit the Silect MCP Client .env configuration file and add whichever MCP servers you would like added.

Here is an example of adding an open source ServiceNow MCP:

# ServiceNow MCP

DRIVER_MCP_STDIO_SERVERS=ServiceNowMCP|python -m servicenow_mcp.cli –instance-url https://<instance-name>.service-now.com/ –username <username> –password <password>

In some cases you will need to set the Silect MCP Client service to a delayed start if you are adding other MCPs servers which take time to startup.