head to head · open source

Bruno vs mcpo

Bruno has 47,992 GitHub stars, 3,068 forks, 1,831 open issues and last shipped yesterday. mcpo has 4,414 stars, 508 forks, 56 open issues and last shipped 6 months ago. Bruno leads on adoption by 987% (47,992 vs 4,414 stars). Bruno is written in JavaScript under MIT; mcpo is written in Python under MIT. Bruno has attracted 6% as many forks as stars, mcpo 12%. Bruno was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (openapi), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

Bruno ★ 48K mcpo ★ 4.4K category Developer Tools

← all 20902 open source comparisons

Side by side

Bruno mcpo
GitHub stars ★ 48K ★ 4.4K
License MIT MIT
Written in JavaScript Python
Last push 2026-11-02 2026-05-17
Forks ⑂ 3.1K ⑂ 508
Self-hosting Yes Yes
Data ownership Your server Your server

pick Bruno if

  • You weight community size — 48K stars and counting
  • You want the MIT license terms
  • Your stack matches JavaScript
  • You value the larger contributor base for long-term maintenance

full Bruno profile →

pick mcpo if

  • You want the mcpo feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Python
  • You evaluated both and mcpo fits your workflow better

full mcpo profile →

About Bruno

Bruno Opensource IDE for exploring and testing APIs. English Українська Русский Türkçe Deutsch Français Português (BR) 한국어 বাংলা Español Italiano Română Polski 简体中文 正體中文 العربية 日本語 ქართული Nederlands فارسی Bruno is a new and innovative API client, aimed at revolutionizing the status quo represented by Postman and similar tools out there. Bruno stores your collections directly in a folder on your filesystem. We use a plain text markup language, Bru, to save information about API requests. You can use Git or any version control of your choice to collaborate over your API collections. Bruno is offline only. There…

read the full Bruno overview →

About mcpo

⚡️ mcpo Expose any MCP tool as an OpenAPI compatible HTTP server—instantly. mcpo is a dead simple proxy that takes an MCP server command and makes it accessible via standard RESTful OpenAPI, so your tools "just work" with LLM agents and apps expecting OpenAPI servers. No custom protocol. No glue code. No hassle. 🤔 Why Use mcpo Instead of Native MCP? MCP servers usually speak over raw stdio, which is: 🔓 Inherently insecure ❌ Incompatible with most tools 🧩 Missing standard features like docs, auth, error handling, etc. mcpo solves all of that—without extra effort: ✅ Works instantly with OpenAPI tools, SDKs, and…

read the full mcpo overview →

More in Developer Tools

Related comparisons

More API Development & Testing projects

Compare either of these against the rest of the API Development & Testing field.

Frequently asked questions

Is Bruno or mcpo more popular?

Bruno has 47,992 GitHub stars and mcpo has 4,414. Bruno has the larger community by that measure.

Are Bruno and mcpo free?

Both are open source. Bruno is licensed under MIT and mcpo under MIT. Neither carries a licence fee.

What is the difference between Bruno and mcpo?

Bruno is written in JavaScript and mcpo in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, Bruno or mcpo?

Choose Bruno if you want the larger community (47,992 stars) or its MIT licence terms. Choose mcpo if its feature set, stack or MIT licence fits better. Both are self-hostable.