mikrotik-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MIKROTIK_MCP_CONFIG | No | Optional path or colon-separated list of paths to config files. Overrides the default config search path. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mikrotik_list_profilesA | Search the configured MikroTik router profiles. Config files are re-read on every call. Returns connection details and whether each profile is read-only. Never returns secrets — passwords and passphrases live in environment variables, and only the variable name is shown. Call this first to discover the profile name that mikrotik_exec needs. |
| mikrotik_execA | Run a single RouterOS command on a configured router over SSH and return its output. Stateless: each call opens a fresh connection and closes it before returning, so there is no session, working directory or shell state carried between calls — send absolute command paths such as '/system resource print'. Profiles are read-only by default, in which case commands that would change the router are refused before connecting. Use mikrotik_list_profiles to find profile names. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
mikrotik_list_profiles and mikrotik_exec have completely distinct purposes: one discovers connection profiles, the other executes RouterOS commands. The descriptions even cross-reference each other, making misselection very unlikely.
Both tools share a consistent mikrotik_ prefix and use snake_case, which is good. However, list_profiles follows a verb_noun pattern while exec is a bare verb without an object, a minor style inconsistency.
At two tools, the count is slightly below the typical 3-15 range, but the split is sensible: one tool for discovery and one for execution. Each tool earns its place for the server's narrow purpose.
For a server whose stated purpose is running RouterOS commands on configured profiles, the surface is complete: discover profiles, then execute commands. There are no obvious missing operations, and the stateless/read-only behavior is handled clearly.