MikroTik MCP Server Integration

What does “MikroTik” MCP Server do?

The MikroTik MCP (Model Context Protocol) Server acts as a bridge between AI assistants and MikroTik RouterOS devices. It enables AI-based systems to communicate with and control MikroTik routers using natural language requests. This server facilitates the execution of essential networking tasks such as managing VLANs, configuring firewall rules, handling DNS settings, and more. By connecting AI assistants with MikroTik devices, the MikroTik MCP Server streamlines complex router management, automates network configuration, and enhances the efficiency of network administrators and developers working with MikroTik infrastructure.

List of Prompts

No explicit prompt templates are mentioned in the available repository documentation or code.

List of Resources

No explicit resources exposed by the MikroTik MCP Server are listed in the available documentation.

List of Tools

• mikrotik_create_vlan_interface
  Creates a VLAN interface on a MikroTik device. Parameters include interface name, VLAN ID, parent interface, and optional settings like comment, disabled state, MTU, service tag, ARP, and ARP timeout.

• mikrotik_list_vlan_interfaces
  Lists VLAN interfaces on the MikroTik device. Supports optional filters for name, VLAN ID, parent interface, and disabled status.

• mikrotik_get_vlan_interface
  Retrieves detailed information about a specific VLAN interface using its name.

• mikrotik_update_vlan_interface
  Updates the properties of an existing VLAN interface, including its name, VLAN ID, parent interface, and description.

Use Cases of this MCP Server

• Automated VLAN Management
  Effortlessly create, list, update, and retrieve details of VLAN interfaces on MikroTik routers, reducing manual configuration errors and saving time for network engineers.

• Integration with AI Assistants
  Enable voice or text-based AI assistants to manage router configurations in real-time, making network operations more accessible for non-expert users.

• Network Configuration Auditing
  Quickly fetch and review current VLAN interface configurations to ensure compliance with network policies and standards.

• Bulk Configuration Updates
  Perform batch updates on multiple VLAN interfaces efficiently via automated scripts or AI-driven workflows.

How to set it up

Windsurf

1. Ensure Python 3.8+ and MikroTik RouterOS device with API access are available.
2. Install dependencies (see README for specific requirements).
3. Add the following to your Windsurf configuration file:

   {
     "mcpServers": {
       "mikrotik-mcp": {
         "command": "mcp-server-mikrotik",
         "args": []
       }
     }
   }
   

4. Save the config and restart Windsurf.
5. Verify the MCP server is running and accessible.

Securing API keys example:

{
  "mcpServers": {
    "mikrotik-mcp": {
      "command": "mcp-server-mikrotik",
      "env": {
        "MIKROTIK_API_PASSWORD": "${MIKROTIK_API_PASSWORD}"
      },
      "inputs": {
        "username": "${MIKROTIK_API_USER}"
      }
    }
  }
}

Claude

1. Install Python 3.8+ and required dependencies.
2. Add the MCP server to Claude’s configuration:

   {
     "mcpServers": {
       "mikrotik-mcp": {
         "command": "mcp-server-mikrotik",
         "args": []
       }
     }
   }
   

3. Save and restart Claude.
4. Check MCP server connectivity.

Securing API keys example:

{
  "mcpServers": {
    "mikrotik-mcp": {
      "command": "mcp-server-mikrotik",
      "env": {
        "MIKROTIK_API_PASSWORD": "${MIKROTIK_API_PASSWORD}"
      },
      "inputs": {
        "username": "${MIKROTIK_API_USER}"
      }
    }
  }
}

Cursor

1. Meet prerequisites (Python 3.8+, RouterOS device).
2. Configure the MCP server in Cursor:

   {
     "mcpServers": {
       "mikrotik-mcp": {
         "command": "mcp-server-mikrotik",
         "args": []
       }
     }
   }
   

3. Save configuration and restart Cursor.
4. Test connection with the MCP server.

Securing API keys example:

{
  "mcpServers": {
    "mikrotik-mcp": {
      "command": "mcp-server-mikrotik",
      "env": {
        "MIKROTIK_API_PASSWORD": "${MIKROTIK_API_PASSWORD}"
      },
      "inputs": {
        "username": "${MIKROTIK_API_USER}"
      }
    }
  }
}

Cline

1. Confirm Python 3.8+ and RouterOS device with API access.
2. Edit the Cline configuration file:

   {
     "mcpServers": {
       "mikrotik-mcp": {
         "command": "mcp-server-mikrotik",
         "args": []
       }
     }
   }
   

3. Save the configuration and restart Cline.
4. Ensure the MCP server is reachable.

Securing API keys example:

{
  "mcpServers": {
    "mikrotik-mcp": {
      "command": "mcp-server-mikrotik",
      "env": {
        "MIKROTIK_API_PASSWORD": "${MIKROTIK_API_PASSWORD}"
      },
      "inputs": {
        "username": "${MIKROTIK_API_USER}"
      }
    }
  }
}

How to use this MCP inside flows

Using MCP in FlowHunt

To integrate MCP servers into your FlowHunt workflow, start by adding the MCP component to your flow and connecting it to your AI agent:

Click on the MCP component to open the configuration panel. In the system MCP configuration section, insert your MCP server details using this JSON format:

{
  "mikrotik-mcp": {
    "transport": "streamable_http",
    "url": "https://yourmcpserver.example/pathtothemcp/url"
  }
}

Once configured, the AI agent is now able to use this MCP as a tool with access to all its functions and capabilities. Remember to change “mikrotik-mcp” to whatever the actual name of your MCP server is and replace the URL with your own MCP server URL.

Overview

Our opinion

The MikroTik MCP server provides a focused set of tools for VLAN interface management and is well documented for setup on multiple platforms. However, it lacks explicit resources and prompt templates, and there is no mention of Roots or Sampling support. Overall, it is a practical server with clear utility for network administrators, but limited in broader MCP feature coverage.

MCP Score

Rating: 5/10
The server is functional and well-documented for its use case but does not leverage the full breadth of MCP features such as resources, prompt templates, Roots, or Sampling, which limits its flexibility and integration potential in more complex MCP-driven workflows.