Autoeval
Uses OpenAI models to act as judges and evaluators for AI application evaluations, allowing configuration of judge and primary model IDs.
Supports evaluating agent traces in OpenTelemetry format, enabling analysis of agent-trace results and trajectories.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Autoevalrun the release gate suite on my CI manifest before deploying"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Demo
![]()
Quickstart, validate the setup, and see passing and failing release gates.
Autoeval is an open-source CLI and MCP server that turns committed evaluation files into versioned, gated checks on AI-agent behavior, scored by the Plumloom backend. It runs from your terminal, your CI, or your coding agent.
A single evaluation tells you what happened. Repeated evaluation tells you what would happen again.
LLM outputs and judge scores vary between runs, so one passing score is one sample. Autoeval reports reliability evidence — confidence intervals and consistency statistics — so a release decision rests on more than a single number.
Related MCP server: AI Workbench MCP
What you can evaluate
Scenario | Conversation | Agent trace | |
Supported evaluation context | ✅ | ✅ | ✅ |
Multiple trials — confidence intervals and consistency statistics | ✅ | — | — |
Multiple trials and statistical reliability evidence apply toscenario evaluations. Autoeval also supports conversation and agent-trace evaluation contexts.
Where it runs
| Author, validate, and run eval files; read scored results from the terminal. |
| A suite manifest lists evals and thresholds. |
| A local stdio MCP server exposes the same action layer as the CLI. |
| Connect OpenAI or Together.ai so Plumloom can run evaluations. |
Eval files and the suite manifest are the only inputs you author and commit. Autoeval submits runs to Plumloom, reads back scored results, and the gate turns them into a CI pass/fail.
Quickstart
Requirements: Node.js 22.13+ and a Plumloom CLI key (pl_sk_…). pnpm 11 only if building from source.
Connect an AI provider (OpenAI or Together.ai).
npm install --global @plumloom/cli
autoeval login
autoeval quickstartquickstart resolves a workspace and judge model, grades a bundled sample end to end, and prints the result. Autoeval connects to https://api.plumloom.ai automatically. → Quickstart guide
pnpm install --frozen-lockfile && pnpm buildIn the examples below, replace autoeval with node packages/cli/dist/cli.js when running from this repository.
File-driven evaluation
An evaluation file uses the configured-run JSON accepted by autoeval eval validate. Artifact and reference-document paths resolve relative to the evaluation file.
{
"methodology": { "judgeModelId": "<judge-model-id>", "evaluatorInstructions": "..." },
"configuration": {
"contextName": "Support conversation",
"contextType": "conversation",
"artifactFile": "./data/conversation.json",
"referenceDocumentFiles": ["./policy/refunds.md"]
}
}autoeval eval validate --input support.autoeval.json
autoeval eval create-from --workspace <workspace-id> --input support.autoeval.json --runModel-ID fields take UUIDs; copy enabled IDs from autoeval models. → Write and run your own evaluation file
Gate a release in CI
A suite manifest names a workspace, lists evaluation files, and declares release thresholds.
workspace: <workspace-id>
gate:
minOverall: 4.0
minScenario: 3.5
evals:
- ./evals/refund-policy.autoeval.json
- file: ./evals/support-conversation.autoeval.json
gate:
metrics:
factuality: 4.0
relevance: 3.8autoeval doctor --manifest autoeval.suite.yaml # read-only pre-flight
autoeval suite run --manifest autoeval.suite.yaml # run, no release judgment
autoeval suite gate --manifest autoeval.suite.yaml # apply thresholdsVerdict |
|
|
|
Exit code |
|
|
|
Commit the manifest, every referenced eval file, and any artifacts or reference documents those evals load. Start from examples/suite/autoeval.suite.yaml and its fixtures under examples/smoke/fixtures/, then use autoeval workspace list and autoeval models to replace the synthetic IDs.
Copy .github/workflows/autoeval-suite-gate.yml.example into your repository for a ready-to-use workflow. See Gate a release in CI and Release gating for CI.
For same-repository pull requests, the example workflow also updates one context-aware Autoeval Reliability Report comment per suite and matrix job, showing the gate verdict alongside available Standard, Judgment, and Repeatability evidence. Comment failures never replace the gate verdict or exit code. Fork pull requests are excluded because they do not receive repository secrets.
autoeval workspace list
autoeval models
autoeval results <evaluation-id> <run-id>
autoeval --json results <evaluation-id> <run-id>See the command guide, CLI reference, developer guide, and .env.example. Smoke workflows: examples/smoke/ · sample configs: examples/evals/.
Use it from your coding agent
MCP server — a local stdio server exposing the same action layer as the CLI. Credentials resolve from AUTOEVAL_API_KEY, then the OS credential store; it never prompts. → MCP guide · Codex & Claude Code
Claude Code plugin
claude plugin marketplace add AlchemyInCode/plumloom-autoeval-oss
claude plugin install plumloom-autoeval@plumloomGemini CLI extension (skill-only for now: install and trigger supported, end-to-end execution not yet)
gemini extensions install https://github.com/AlchemyInCode/plumloom-autoeval-oss→ Agent skill guide · Security and permissions
Free Autoeval Pilot
Limited to ten teams. Complimentary hands-on onboarding, evaluation support, and model access. Applications are considered in the order received. Sign up for the Free Pilot →
Documentation
Get started | Integrate | Operate |
Support
Privacy policy: Plumloom Privacy Policy
Support: support@plumloom.ai
This server cannot be deployed
Maintenance
Related MCP Connectors
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax.
QA platform for agents: coverage signals, in-repo test plans, verified tests and release governance.
- Divinci AIOAuthai.divinci
Release management and QA for custom AI assistants: RAG, releases, scored QA, signed TrustBench runs
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
Related MCP Servers
AlicenseNot gradedqualityCmaintenanceProvides advanced evaluation tools for assessing AI safety, alignment, and performance of LLM outputs. Enables programmatic evaluation of quality, safety metrics like toxicity and PII detection, and operational metrics including carbon footprint and cost estimation.4Apache 2.0- AlicenseCqualityDmaintenanceEnables acceptance gates for AI coding-agent runs by recording evidence, running deterministic validation, applying a quality gate, and rendering auditable outcomes.734 PyPIApache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides SDLC compliance verification as tools that AI agents can invoke, continuously monitoring and evaluating development processes.MIT
- AlicenseNot gradedqualityBmaintenanceEnables evidence-first release readiness assessment by running or accepting build, API, browser, visual, performance, and security evidence, then returning SHIP, REVIEW, or HOLD recommendations with clustered regressions.1 npmApache 2.0