n8n MCP Client Tool with rConfig: AI workflows over your network configs

n8n MCP Client Tool with rConfig: AI workflows over your network configs

n8n’s AI Agent node can use rConfig’s MCP server as a tool through the MCP Client Tool, with a bearer credential and the HTTP Streamable transport. Pair it with rConfig’s webhooks and you get event-driven AI: a config changes, n8n wakes up, the agent explains the change, and the summary lands in Slack, Teams or a ticket. No one has to ask.

Best for: automation teams already on n8n, event-driven summaries, joining rConfig with ticketing and chat without writing code.

Connect

In an AI Agent node, add an MCP Client Tool and set:

Use a token from a dedicated rConfig user whose role covers only the devices the workflow needs. Every run uses that user’s access, whoever triggered it.

Event-driven: explain every config change

rConfig’s webhooks post a config.changed event the moment a backup differs from the previous version. The Generic JSON payload already carries the device, the config ID, the command and the diff lines.

flowchart LR
    R["rConfig<br/>config.changed webhook"] --> W["n8n Webhook trigger<br/>(verify signature)"]
    W --> A["AI Agent<br/>+ rConfig MCP Client Tool"]
    A --> S["Slack / Teams / ticket"]

1. Trigger: an n8n Webhook node receives the event. Check the signature rConfig sends before going further (see Verify the signature).
2. Agent: pass data.device.name, data.config.id and the diff to the AI Agent with a prompt such as: “Explain this config change on {{ device }} for the network team: what changed, what it affects, and whether it looks risky. Use rConfig to look at the device’s recent history if the diff alone isn’t enough.”
3. Output: send the agent’s answer to a Slack or Teams node, or create a ticket.

The webhook gives the agent the diff for free, so most runs need only one or two MCP calls. The rConfig tools are there for context: earlier versions, the full config, compliance status.

Other workflows

• Nightly compliance digest: a Schedule trigger asks the agent for the compliance status of each critical group and posts a short summary each morning.
• Ticket enrichment: when a ServiceNow or Jira change ticket names a device, the agent adds that device’s recent config history and current compliance to the ticket.
• Chat question box: an n8n Chat trigger in front of the agent gives a team a simple “ask rConfig” box, within the service user’s device access.

Related reference

• Webhooks
• Connect an AI agent over MCP
• Which AI agents can connect to rConfig?
• Alert to root cause