The Sematext MCP Server got support for another tool: get_network_map

The get_network_map tool relies on Network Map to return the live network topology showing how your services and hosts are connected. This lets the AI agent understand your infrastructure layout and reason about blast radius, traffic patterns, connectivity issues, etc. An AI agent can call get_network_map with optional filters (such as the host/service name, status, namespace, cluster, environment, etc.) and get back a graph structure it can interrogate with prompts such as:

• What’s connected to my payment service?
• What does the production namespace look like?
• What depends on PostgreSQL?
• Which HTTP services are producing the most 4xx or 5xx errors?
• Which network connections are experiencing packet loss?
• What services generate or receive the most data over the network?
• What services are running in Kubernetes?
• …

With this tool, and when you have Network Map enabled in your Sematext account, your AI agent can have a view of the network topology and understand how the different services are interlinked. This lets it avoid wasting time (and your tokens) looking into things that have nothing to do with the source of a live incident.

The tool returns live network topology. This means it should be used for handling live incidents or just understanding of the running system, and not for troubleshooting historical data.

Start Free Trial