Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y @orangepro/[email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
OPENAI_API_KEY=<secret> ANTHROPIC_API_KEY=<secret> OLLAMA_BASE_URL=<value> claude mcp add ai.orangepro-mcp -- npx -y @orangepro/mcp-server@0.2.60Run in a terminal.
{ "mcpServers": { "ai.orangepro-mcp": { "command": "npx", "args": [ "-y", "@orangepro/[email protected]" ], "env": { "OPENAI_API_KEY": "<secret>", "ANTHROPIC_API_KEY": "<secret>", "OLLAMA_BASE_URL": "<value>" } } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
OrangePro maps every public function in your repository, links each one to the tests that actually call it, and ranks what's left by what it can break. For a test you care about, it breaks the function in an isolated copy and checks that the test fails. It runs on your machine, uses no AI model for scoring, and sends nothing to OrangePro. Model calls happen only if you add your own key, for optional test generation and suggestions.
npx -y @orangepro/mcp-server@latest start .
Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.
Every run writes two reports and a spreadsheet of tests to .orangepro/:
Every function gets one of four things to do:
Both from OrangePro run on its own repository at commit 64a5213, without a model key, so no tests were drafted. With a key, each of the top 20 shows two drafted tests, and the side panel shows their steps and code.
opro prove replaces the function body with a fixed return value in an isolated copy and reruns your own test, unchanged. If the test still passes, it wasn't protecting that function.cd /path/to/your/repo
# install the repo's own dependencies first (npm ci, uv sync, go mod download, ...)
npx -y @orangepro/mcp-server@latest start .
open .orangepro/short_behavior-coverage.html
Analysis, ranking and proof need no model key. Test generation is optional and uses your own key (see Model setup).
Tips for the most accurate run:
rank_exclude_paths (see Configuration).start reuses the last reports at once and says so; --fresh runs in full anyway.What's written:
.orangepro/
├── short_behavior-coverage.html ← one-page summary
├── behavior-coverage.html ← detailed report: worklist, map, run details
├── tests.csv ← drafted tests, one row per test
├── report-data.json ← the data both reports show (used to compare and reuse runs)
├── run-key.json, last-start.json ← what the last run saw, so an unchanged repo is not analysed again
├── graph.json ← the evidence graph (deterministic)
├── ledger.json ← proof certificates
├── rtm.md ← traceability matrix
└── config.json ← optional per-repo settings
orangepro_generated/ ← generated tests (only with a model key); your files are never edited
Every function gets exactly one evidence label. The four things to do above are read from it.
A proof that ran and did not catch the break turns the function into Write; a proof made before the code changed turns it back into Prove.
What OrangePro doesn't count, so linked numbers are a floor, not a coverage percentage:
Check the tests before writing new ones for a flagged path.
"Proven 0" is normal on a first run. Proof runs your tests, so it happens only for the functions you choose, or within the attempt budget of
opro start.
Each unproven function gets an OrangePro Risk Score, ORS = P × I × D:
The score sets the order of work. It is not a defect probability. The weights are fixed and no AI model is involved. The report shows the inputs behind every row.
# Python: the mutation value is derived from the function (return annotation or its observed result)
opro prove-loop --target-symbol 'sym:app/billing/invoices.py#void_invoice' \
--test 'tests/test_invoices.py::test_void_marks_invoice_void' --replacement sentinel
# TypeScript / JavaScript: give the inert body to substitute
opro prove-loop --target-symbol 'sym:src/orders.service.ts#OrdersService.cancel' \
--test src/orders.service.spec.ts --replacement 'return null;'
Find weak tests without a model key:
opro roast . # passing tests whose targeted mutant still survives
OrangePro runs as an MCP server. Add it to your client's config:
{
"mcpServers": {
"orangepro-local": {
"command": "npx",
"args": ["-y", "@orangepro/mcp-server@latest", "mcp"]
}
}
}
A prompt that runs the whole loop:
"Use
orangepro_start, thenorangepro_find_test_gaps. For the top gap, write a test at the suggested path, run it, then callorangepro_prove_loopand tell me whether it was proven."
Optional. Put it in .orangepro/config.json in the repository, or in ~/.orangepro/config.json for defaults across repositories. Every setting that changes the ranking is shown in the report.
{
"classification": {
"rank_exclude_paths": ["ui/**", "docs/**", "scripts/**"],
"test_support_paths": ["internal/testutil/**"],
"destructive_sinks": ["archive*"]
},
"tuning": { "churn_window_days": 180 },
"proof": { "python_runner": "auto", "attempt_limit": 20 },
"overrides": [
{ "symbol": "sym:src/legacy/shim.ts#shim", "action": "suppress", "reason": "generated shim, not product code" }
]
}
rank_exclude_paths removes paths from the ranking. They are still counted as behaviors.destructive_sinks adds delete-like calls for your codebase.suppress, pin, reclassify) each require a reason, and the report lists them..venv or venv, then uv or poetry when their lock files are present, else python -m pytest. Set proof.python_runner to use your own command.npm ci, uv sync, go mod download, mvn -q install, …). Proof runs your own tests in an isolated copy and needs them to pass there..gitignore or .orangeproignore (negations with ! aren't supported), the usual build and dependency folders (node_modules, vendor, dist, build, target, coverage, .venv, …), files over 1 MB, and generated code (files marked Code generated … DO NOT EDIT). Up to 100,000 files; ORANGEPRO_MAX_FILES lowers that and ORANGEPRO_MAX_ANALYZE_MS sets a time limit for the scan.start options, whether a model key is set, and the analysis version. A run whose test drafting failed on a provider error (out of credits, rate limit) runs again in full..env.provider.local, .env.local or .env file in the repository, and OrangePro never writes them anywhere. opro setup saves only the provider and model name.tests.csv include the tests your model drafted, and the prompts include the function names, files and evidence they're based on.Reports include a Give feedback link and a This looks wrong link on each finding. Once in a while, after the findings, they also ask whether the report helped.
opro feedback # print the link and your settings
opro feedback off # stop the "Did this help?" question (links stay)
ORANGEPRO_FEEDBACK_URL=off # hide every feedback link
The question appears at most once every 14 days (ORANGEPRO_FEEDBACK_COOLDOWN_DAYS). That preference is stored only on your machine. MCP clients get the link as optional result metadata (_meta["ai.orangepro/feedback_url"]), and your agent is never asked to prompt you for feedback.
opro # same as opro start .
opro start . --no-ai --no-auto # analyze + reports, no model calls, no proof attempts
opro start . --fresh # run in full even when nothing changed since the last run
opro start --base main # scope to a branch diff
opro analyze # build the evidence graph and reports
opro gaps --limit 10 # top unproven behaviors, ranked
opro prove-loop ... # mutation proof for one function (see above)
opro roast . # find tests whose mutant survives (no key needed)
opro doctor --proof # why top targets aren't proven yet
opro generate --base main # tests for what this branch changed (needs a model key)
opro rtm # traceability matrix
opro export # metadata-only evidence pack
opro coverage # find or generate runtime coverage artifacts
opro feedback [on|off] # feedback link and invitation setting
opro mcp # run as an MCP server (stdio)
Add --json to any read command for machine output. Run opro help for every flag.
Run your own unit and integration coverage first, then opro start. OrangePro ingests Go coverprofiles, lcov, coverage.py XML and JaCoCo XML, and keeps unit, integration and unclassified coverage separate. To label artifacts, add .orangepro/coverage-suites.json:
{
"artifacts": {
".orangepro/coverage/unit.coverprofile": { "suite": "unit", "command": "make unit-test-coverage" },
".orangepro/coverage/integration.coverprofile": { "suite": "integration", "command": "make integration-test-coverage" }
}
}
Auto-detect order: OpenAI → Ollama → Anthropic. Override with --provider and --model, or run opro setup.
orangepro_generated/ with the files and existing tests they're grounded on, and where and how to run them.One row per test, UTF-8. The first 12 columns are for import; the rest keep the priority, evidence and proof command with each test. Priority is High for the five highest-ranked functions and Medium for the rest.
opro generate --base main # tests for what this branch changed (read-only git diff)
opro generate --changed # current branch vs its base
opro generate --pr 1234 # checks out PR #1234 (asks first; refuses on a dirty tree)
This repository is the free local tool. The OrangePro platform adds:
git clone https://github.com/OrangeproAI/orangepro-mcp.git
cd orangepro-mcp && npm ci && npm run build
npm test
PRs welcome. Please open an issue first for large changes.
© 2026 MCP Directory.
Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.
{ "mcpServers": { "ai.orangepro-mcp": { "command": "npx", "args": [ "-y", "@orangepro/[email protected]" ], "env": { "OPENAI_API_KEY": "<secret>", "ANTHROPIC_API_KEY": "<secret>", "OLLAMA_BASE_URL": "<value>" } } }}Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
The publisher lists these environment variables: OPENAI_API_KEY, ANTHROPIC_API_KEY, OLLAMA_BASE_URL.
OrangePro runs locally over stdio.
Last checked 2026-11-14. Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.