# rosetta [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/tikoci/rosetta  
**GitHub Stars:** 54  
**npm Downloads (last month):** 2217  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rosetta

## Description
MCP Server with RouterOS docs + commands + products + changelogs, using SQLite-as-RAG, sourced from MikroTik

## Tools
Capabilities this server exposes over MCP:

- **routeros_search** — Start here.** Unified search with input classifier — returns pages + related callouts, videos, properties, changelogs, devices, skills
- **routeros_get_page** — Full page content by ID or title, section-aware for large pages
- **routeros_lookup_property** — Property by exact name — type, default, description
- **routeros_explain_command** — Read-only explanation for a CLI command — canonical path/verb, args, warnings, docs, changelogs
- **routeros_command_tree** — Browse the command hierarchy (`/ip/firewall/filter` style)
- **routeros_search_changelogs** — Changelogs filtered by version range, category, breaking flag
- **routeros_command_version_check** — Which RouterOS versions include a command path
- **routeros_command_diff** — Added/removed commands between two RouterOS versions
- **routeros_device_lookup** — Hardware specs — filter by architecture, RAM, PoE, wireless, etc.
- **routeros_search_tests** — Cross-device ethernet and IPSec benchmarks
- **routeros_dude_search** — FTS across archived Dude wiki docs (separate from RouterOS search)
- **routeros_dude_get_page** — Full Dude wiki page by ID or title, with screenshot metadata
- **routeros_stats** — Database health and coverage stats
- **routeros_current_versions** — Live-fetch current RouterOS versions from MikroTik

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `bunx` (confidence: high):

```json
"mcpServers": {
  "rosetta": {
    "command": "bunx",
    "args": ["@tikoci/rosetta"]
  }
}
```

## Documentation

## What rosetta does

rosetta gives MCP clients access to MikroTik RouterOS reference material and related hardware data. Its main corpus includes RouterOS v7 documentation pages, CLI Reference properties, versioned command trees, command arguments, changelogs, product specifications, performance tests, YouTube transcript segments, and documentation callouts such as warnings and tips. A separate search area covers archived Dude wiki pages.

The server is intended for questions that benefit from structured RouterOS reference data rather than general web search. It can identify the canonical path and verb for a CLI command, explain its arguments and warnings, inspect a property’s type and default, compare command availability between RouterOS versions, and locate devices by hardware characteristics.

## How it works

SQLite FTS5 provides the retrieval layer. Search uses SQL-based full-text matching with BM25 ranking and porter stemming, which suits exact technical terms such as `dhcp-snooping` and `/ip/firewall/filter`. The database is a local file, so the search process does not require an API key or a separate vector database.

Documentation prose is sourced from MikroTik’s live Docusaurus manual during release builds. Property and command information can come from either the manual or the CLI Reference, with the response identifying the source. The command hierarchy is built from RouterOS inspection data. `routeros_current_versions` fetches current RouterOS versions directly from MikroTik, while most other queries use the local database.

## Setup and configuration

For local use, install Bun and run:

```sh
bunx @tikoci/rosetta --setup
```

The setup command downloads the database and prints configuration snippets for supported MCP clients. Run it before starting the client so the initial database download does not delay the MCP handshake. A database refresh can be requested with `--refresh`; stop clients that use the database before refreshing it. The package also provides a `@next` channel for prerelease builds.

RouterOS 7.22 or later can run rosetta through the `/app` container feature on supported x86 or ARM64 devices. The container package, device mode, and an `/app` storage disk are required, with at least 2 GB of free space recommended. The supplied app configuration exposes the MCP service on port 9803 and uses the `/mcp` path. MikroTik can provide an HTTPS URL through its managed certificate service; HTTP is also available, including for CHR installations without the required cloud service.

A local installation communicates over stdio. A router installation exposes an HTTP-capable MCP endpoint, whose UI URL can be retrieved from WebFig or with `/app/get rosetta ui-url`. The database can also be searched from the router through its terminal browser.

## Tools and capabilities

- `routeros_search` performs unified searches across pages, callouts, videos, properties, changelogs, devices, and skills.
- `routeros_get_page` retrieves complete pages by ID or title and can return sections from large pages.
- `routeros_lookup_property` finds an exact property and returns its type, default, and description.
- `routeros_explain_command` provides read-only command explanations with paths, verbs, arguments, warnings, documentation, and changelog references.
- `routeros_command_tree` navigates the RouterOS CLI hierarchy.
- `routeros_search_changelogs`, `routeros_command_version_check`, and `routeros_command_diff` support version research.
- `routeros_device_lookup` searches hardware specifications by attributes such as architecture, memory, PoE, and wireless capability.
- `routeros_search_tests` locates Ethernet and IPSec benchmarks across devices.
- `routeros_dude_search` and `routeros_dude_get_page` search and retrieve archived Dude wiki content.
- `routeros_stats` reports database health and coverage, while `routeros_current_versions` retrieves current RouterOS versions.

## Limitations and notes

The documentation corpus covers RouterOS v7. The local database is release-specific and can be refreshed when a newer database is available. Database contents and counts therefore depend on the package or container build in use. RouterOS `/app` deployment requires a compatible RouterOS version, architecture, container setup, device mode, and storage disk. On CHR, the system disk cannot be used for `/app` storage, and free or trial mode may require HTTP instead of HTTPS.

_Full upstream README: https://allmcps.com/mcp/rosetta/readme_