Skip to content

MCP-Bridge vs x64dbg-mcp-server

MCP-Bridge is an open-source MCP server for ai models and llm tooling. x64dbg-mcp-server is an open-source MCP server for ai models and llm tooling.

  • x64dbg-mcp-server has more GitHub stars (2,841 vs 922).
  • MCP-Bridge is best for give a chat front end that lacks mcp support access to tools such as web fetch.
  • x64dbg-mcp-server is best for letting an ai assistant set breakpoints and step through a binary while analysing it.
What it is
MCP-Bridge is an open-source MCP server for ai models and llm tooling.
x64dbg-mcp-server is an open-source MCP server for ai models and llm tooling.
Best for
Give a chat front end that lacks MCP support access to tools such as web fetch
Letting an AI assistant set breakpoints and step through a binary while analysing it
Kind
MCP server
MCP server
Pricing
Open source
Open source
Platforms
API, self-hosted, Web
Windows, API, self-hosted
GitHub stars
922
2.8K
Last commit
Dec 2025
Nov 2026
License
MIT
MIT
Open source
Good for
Give a chat front end that lacks MCP support access to tools such as web fetch; Test whether MCP server configuration works by listing tools through the API or SSE endpoint; Run a local model served by vLLM or Ollama with MCP tools attached
Letting an AI assistant set breakpoints and step through a binary while analysing it; Dumping registers, call stacks and memory during a live debugging session; Triaging a packed executable by detecting its original entry point and dumping modules

What MCP-Bridge does

  • OpenAI-compatible chat endpoints

    Chat completions, both streaming and non-streaming, are served with MCP tools available to the model.

  • Config-driven MCP servers

    MCP servers are declared in a JSON config file, loaded from a mounted file, a URL, or an environment variable.

  • SSE bridge for MCP clients

    Exposes the aggregated tools over SSE so MCP-aware clients can connect to the bridge as a server.

  • API key authentication

    Optional bearer-token checks can be enabled in the config to restrict access to the server.

  • REST endpoints for MCP primitives

    Exposes REST routes for interacting with MCP features, documented through the built-in OpenAPI docs.

  • MCP sampling support

    The README lists MCP sampling as a working feature, routed to configured models with cost and speed weights.

What x64dbg-mcp-server does

  • Broad debugger tool coverage

    The README lists 84 tools covering stepping, breakpoints, memory, registers, modules, threads, PE analysis and tracing, while the tools table lists 72.

  • Dual HTTP transports

    Supports Streamable HTTP and SSE so both current and legacy MCP clients can connect.

  • Bearer token authentication

    A token is generated on first run and required on every request, and can be rotated from the config dialog.

  • No runtime dependencies

    Built with Zig as a single native binary, with no .NET, Python or other runtime needed.

  • Cross-architecture builds

    One build command produces x32 and x64 plugin binaries, and cross-compiles Windows plugins from Linux or macOS.

  • In-dialog configuration

    Bind address, port and token are changed from the Plugins menu, and the server restarts on save.

MCP-Bridge vs x64dbg-mcp-server: questions

Is MCP-Bridge or x64dbg-mcp-server cheaper?

Both are open source. Compare current plans on each official site.

What is the difference between MCP-Bridge and x64dbg-mcp-server?

MCP-Bridge is an open-source MCP server for ai models and llm tooling. x64dbg-mcp-server is an open-source MCP server for ai models and llm tooling. x64dbg-mcp-server has more GitHub stars (2,841 vs 922).

Keep comparing