MCP

Settings Dialog

<Prev Schedules Index

MCP

MCP Settings

This tab contains settings for the built-in MCP (Model Context Protocol) server. It enables seamless integration between LLM (Large Language Model) applications and the IPNetwork Monitor service, allowing LLMs to query status and control the system.

The Enable MCP Server checkbox allows you to start or stop the MCP server.

The Connection Settings section determines how the server listens for connections and how it advertises its address to clients:

  • Port – allows you to bind the MCP server to a specific local TCP port (8888 by default).
  • Binding address – specifies the local network interface (IP address) the server will listen on. Use 0.0.0.0 to listen on all available interfaces.
  • External hostname – specifies the public hostname (and optional port) that MCP clients will use to reach this server.
    Note: If you enter a hostname without a port (e.g. abc.ngrok.app), the system will automatically append the local Port configured above.
    If you are using port forwarding or a tunneling service (like ngrok) where the public port differs from the local port, you must specify it explicitly (e.g. abc.ngrok.app:443).
  • MCP endpoint URL – a read-only field displaying the final URL connection string based on the settings above. Copy this URL to your MCP client configuration.

The Access Tokens section defines the security tokens required for clients to authenticate:

  • Read-write token – grants full access to the MCP API, including making changes to the system.
  • Read-only token – grants restricted access, allowing the client only to view data.

You can generate new random tokens by clicking the Generate new button next to each field.

The SSL Certificates section manages secure connections.

Note: The MCP server shares the same SSL certificate configuration as the Web Interface. To change the certificate files, please visit the Web Interface settings tab.

Important: For HTTPS connections to work correctly, the domain name specified in your External hostname field must match the domain name (Common Name) in the SSL certificate. If they do not match, MCP clients may reject the connection due to SSL verification failure.

<Prev Schedules Index