ExecBro vs Prolog Reasoner — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
ExecBro vs Prolog Reasoner
In-depth architectural comparison of the ExecBro and Prolog Reasoner MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
ExecBro
Code Execution · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Prolog Reasoner
Code Execution · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose ExecBro if you need specialized Code Execution tools running via a local process. Choose Prolog Reasoner if your workspace requires Code Execution integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose ExecBro when:
You need dedicated capabilities in the Code Execution domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
ExecBro is categorized under Code Execution and uses a local stdio subprocess. In contrast, Prolog Reasoner belongs to Code Execution using local stdio subprocess. Select ExecBro when you need capabilities focused on code execution and Prolog Reasoner when you require tools for code execution.
Real two-finger pinch-to-zoom** — Android emulator only (iOS in progress)
input_text
Type text — targets and focuses a field itself, or `native:true` for whatever's focused. `replace:true` clears first (Fabric)
dismiss_keyboard
Blur the focused input and close the on-screen keyboard
execute_in_app
Run JS expressions in the app runtime (REPL-style)
ios_screenshot
Take device screenshots — `ios_screenshot` also works on a USB-attached physical iPhone/iPad (capture only)
Prolog Reasoner Tools (5)
execute_prolog
Execute Prolog code and return reasoning results.
Write Prolog facts and rules, then run a query against them.
Supports CLP(FD) constraints, negation-as-failure, and all
standard SWI-Prolog features.
list_rule_bases
List all saved rule bases with description and tags.
Returns ``{"rule_bases": [{"name": str, "description": str,
"tags": list[str]}, ...]}`` sorted by name. Metadata is extracted
from the leading ``% description:`` / ``% tags:`` comments of each
rule base file (see §4.10).
get_rule_base
Retrieve the Prolog source of a saved rule base.
save_rule_base
Save a named rule base containing Prolog rules that can be reused
across ``execute_prolog`` calls.
Use this for stable, reusable knowledge (e.g. ``piece_moves`` for
chess piece movement rules). For one-time facts, include them
directly in ``prolog_code`` instead.