Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Move data between 15+ databases, queues and files at high throughput, without it entering context
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"mq-bridge": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/marcomq/mq-bridge-app:1.4.0",
"mcp",
"--transport",
"stdio"
]
}
}
}Run this in your terminal
claude mcp add mq-bridge -- docker run -i --rm ghcr.io/marcomq/mq-bridge-app:1.4.0 mcp --transport stdioPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mq-bridge": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/marcomq/mq-bridge-app:1.4.0",
"mcp",
"--transport",
"stdio"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mq-bridge": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/marcomq/mq-bridge-app:1.4.0",
"mcp",
"--transport",
"stdio"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account marcomq, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.4.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker, Rust on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server for Georgian public data, read from the organizations that publish it.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
crossing streams
mq-bridge-app is a fast, single-command ETL and data-movement tool built in Rust — and, on top of the same engine, a multi-protocol bridge and traffic workbench for messaging.
It ships in three forms that share one engine and one config format: a desktop app (visual workbench), a CLI / server (headless bridge and one-line copy), and a library (embed the engine in Rust, Python, or Node.js). Design a route once, run it anywhere — no rewrite in between.
Supported integration types include Kafka, RabbitMQ (AMQP), NATS, AWS SQS, MQTT, IBM MQ (optional), HTTP, gRPC, ZeroMQ, MongoDB, sqlx (MySQL, MariaDB, PostgreSQL), and filesystem endpoints.
📖 All documentation lives in the [documentation book](https://marcomq.github.io/mq-bridge/) — installation, quick start, tutorials, cookbook, connector reference, CLI, MCP, and performance tuning. This README is only a short overview; the book is the single source of truth.
At its core is a zero-config copy command that moves data between databases, queues, and files in a single line of bash — no YAML, no pipeline definition, no code:
mqb copy \
'postgres://${PGUSER}:${PGPASSWORD}@localhost/db?table=src&sslmode=disable' \ 'file://out.jsonl?format=raw' \ --filter 'amount > 100' \ --drain
The scheme selects the endpoint and query parameters configure it, so any source→sink pair (Postgres, MySQL, MariaDB, SQLite, NATS, Redis, MongoDB, files, …) is just one URL each. And it's quick.
Use --resume when the source has a safe native position (for example a Kafka consumer group, MongoDB change-stream cursor, Postgres CDC slot, or an explicitly configured SQL cursor). The legacy --from ... --to ... spelling remains supported.
→ Quick start · Connectors · Performance tuning
Test connections and dial in a route in the Postman-inspired UI, export the JSON/YAML, then run that config as a service or from library code. One engine, one config format.
| Form | What it is | Quick install |
|---|---|---|
| Desktop app (UI) | The visual workbench — build/test routes, run request/response traffic, inspect message history | brew install --cask marcomq/tap/mq-bridge |
| CLI / server | Headless binary: a one-line copy, a drain-then-exit batch job, or a long-lived bridge (can also serve the same UI in a browser) | brew install marcomq/tap/mq-bridge-app |
| Library | The engine embedded in your own code — native Rust, Python, or Node.js bindings | cargo add mq-bridge · pip install mq-bridge · npm install mq-bridge |
Learn each form in the book: the three ways to run it · the desktop / web UI · CLI commands · MCP server · library bindings.
brew is the quickest path on macOS and Linux:
brew install marcomq/tap/mq-bridge-app # CLI / server
brew install --cask marcomq/tap/mq-bridge # desktop app
On Windows, install the CLI with cargo binstall mq-bridge-app, or download the desktop installer / CLI from the Releases page. Also available via cargo install mq-bridge-app (from source) and the Docker image ghcr.io/marcomq/mq-bridge-app:latest.
→ Every install method and platform (including the IBM MQ build and Docker) is in the [Install guide](https://marcomq.github.io/mq-bridge/INSTALL.html); to compile from source see Building.
The same binary is an MCP server, so an agent can move data without the rows passing through its context:
mqb mcp install # register with Claude Code / Claude Desktop / Cursor
mcp-name: io.github.marcomq/mq-bridge→ Tools, transports, and the token-cost measurement: [MCP server](https://marcomq.github.io/mq-bridge/MCP.html).
plugins: in the config or --plugin , and use it by name in routes. No special build needed; plugin paths are read only at startup, so adding one means editing the trusted startup configuration and restarting: Native plugins.mqb status for a live table of everything running on the machine.mq-bridge-app's UI overlaps with API clients like Postman, Bruno, Insomnia, and Hoppscotch, but its center of gravity is different: message bridging, runtime operation, and long-lived route management rather than just request composition. Exact feature sets vary by product and edition; this captures the difference in emphasis.
| Capability | mq-bridge | Postman | Bruno | Insomnia | Hoppscotch |
|---|---|---|---|---|---|
| Basic HTTP/API requests | ✓ | ✓ | ✓ | ✓ | ✓ |
| Scripting | — | ✓ | ✓ | ✓ | ✓ |
| Cookie jar | Not yet | ✓ | ✓ | ✓ | ~ |
| Multipart forms | — | ✓ | ✓ | ✓ | ✓ |
| Hex-level payload debugging | ✓ | — | — | — | — |
| Broker pub/sub workflow | ✓ | MQTT | — | — | MQTT |
| Long-lived consumers/routes | ✓ | — | — | — | — |
| Bridge traffic between protocols | ✓ | — | — | — | — |
| Replay messages | ✓ | ~ | — | — | ~ |
| Local-first workspace | ✓ | ~ | ✓ | ✓ | ~ |
| Git-friendly config | ✓ | ~ | ✓ | ✓ | ~ |
| Cloud sync by default | — | ✓ | — | Optional | Optional |
| AI / agent features | — | ✓ | — | ~ | ~ |
| Encrypted config | ✓ | ~ | ~ | ~ | ~ |
Use Postman/Bruno when your main job is crafting and sharing API requests; use mq-bridge-app when you need to connect systems, move messages between protocols, inspect live traffic, and manage bridge-style runtime configuration.
A CSV → JSONL conversion hit 3,134,796 rows/s (mq-bridge 0.4.20) — ~1.5x DuckDB's all-core copy of the same file, on fewer cores and ~18x less memory. The same job through an MCP tool call ran at 3,108,517 rows/s (mq-bridge 1.2.0), level with that session's 3,076,923 rows/s CLI baseline: the MCP interface adds a small fixed request/response cost, not a per-row tax. It costs an agent a *flat* ~385 tokens regardless of row count, because the rows never enter the model's context.
On a Kafka → file relay using mq-bridge-app's default file format and no transform, the same engine was ~78% faster than Sea Streamer comparing both on the mimalloc allocator (~82% against its default-allocator build); the native file-format caveats are detailed in the linked benchmark documentation.
→ Full numbers, methodology, and knobs: Performance tuning and benches/etl/README.md.
For testing, docker-compose files are available for supported backends:
docker-compose -f https://raw.githubusercontent.com/marcomq/mq-bridge/main/tests/integration/docker-compose/postgres.yml up
mq-bridge-app uses the mq-bridge engine *on itself* — the management UI is served through the engine's own HTTP-request/response routing, and the UI form is generated from the Rust config schema (no hand-written form code). See How the app is built.
Active development. Originally the reference implementation and testbed for the mq-bridge engine. The UI/Tauri layer is a working demo rather than a reference implementation — test before relying on it in production.
mq-bridge-app is dual-licensed under either the MIT license or the Apache License, Version 2.0, at your option. Third-party terms for the CLI and desktop distributions are in THIRD_PARTY_LICENSES.txt.