pickfit

BrowseMCP servers

rosetta

MCP server providing searchable MikroTik RouterOS docs, commands, and hardware specs via SQLite.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Bun
  1. Download Bun installer

    curl -fsSL https://bun.sh/install -o /tmp/bun-install.sh
  2. Install Bun runtime required by rosetta

    bash /tmp/bun-install.sh 2>&1; export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH" && bun --version
  3. Install rosetta globally via npm

    export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH" && npm install -g @tikoci/rosetta

Check that it works

export PATH="$HOME/.bun/bin:$HOME/.local/bin:$PATH" && rosetta --version

The output should contain “rosetta 0.12.0”.

Add it to your agent

claude mcp add rosetta -- rosetta
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "rosetta": {
      "command": "rosetta",
      "args": []
    }
  }
}

Add rosetta as an MCP server in your AI client, then ask it questions about RouterOS.

What it does

  • Search the RouterOS documentation
    How to use it
    1. Connect rosetta to your MCP client.
    2. Call the routeros_search tool with a query such as "<your topic>" and an optional limit.
    Tested
  • Browse the command tree and get command explanations
    How to use it
    1. Connect rosetta to your MCP client.
    2. Call the routeros_command_tree tool with a command path such as "<path>" (for example /ip/firewall/filter).
    Tested
  • Look up hardware specs and performance benchmarks
    Not tested
  • Browse the database in a terminal without AI
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 2 of 4 features work
  4. Needs the network

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • Look up DHCP server properties in RouterOS
  • Find setup steps for a bridge VLAN
  • Check command availability in a RouterOS version
  • Show warnings about hardware offloading
  • Compare MikroTik routers by specs, benchmarks, and cost

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Needed the network
  • Checked on 1 Nov 2026
  • Version 0.12.0

An MCP client handshake over stdio listed 14 tools, and a call to routeros_search returned a result.

Differences the test machine hit

  • README: bunx @tikoci/rosetta --setup and bunx @tikoci/rosetta browse
    In the test: Install Bun separately first (curl bun.sh/install) then npm install -g @tikoci/rosetta provides `rosetta` binary on PATH; box PATH needs ~/.bun/bin for Bun runtime
  • README: bunx @tikoci/rosetta browse --once .routeros_search
    In the test: Equivalent is rosetta browse --once .routeros_search; MCP tools provide same search via routeros_search
  • README: install step 2 runs bun-install.sh
    In the test: nothing to change; a note: the box ran bun-install.sh, downloaded, without reading it first, so pickfit did not inspect it

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.