Practical Notes
- Quant: install is
pip install ms-agentwith an optional[research]extra per README. - Quant: validate MCP wiring by calling one tool via an MCP endpoint and logging the round-trip latency (baseline for regressions).
How to use it as a harness (not a demo)
The README example is a good start, but production usage needs guardrails:
- Pin MCP server configs per environment (dev/staging/prod) and store them in version control.
- Separate credentials from configs: env vars only, no secrets checked into repos.
- Replayability: keep a small set of “golden tasks” you can re-run after upgrades to detect regressions.
If your goal is evaluation/security, wrap runs with:
- input/output logging,
- tool-call allow-lists,
- and a cost/latency budget per task.
FAQ
Q: Does it support MCP?
A: Yes. The README includes an example mcpServers config wired into LLMAgent.
Q: How do I keep runs reproducible? A: Pin configs + keep golden tasks + log tool calls and outputs.
Q: What should I do first? A: Wire one simple MCP server endpoint and run a single task end-to-end before adding more tools.