livekit-agent-simulator
Dials any LiveKit voice agent with an AI simulated caller and records a full forensic behavior log.
README
livekit-agent-simulator
Standalone MCP server + CLI (lk-sim) that dials any LiveKit voice agent with an
AI simulated caller (Gemini Live) and records a full forensic behavior log —
transcripts, tool events, flow events, room events — all timestamped per turn.
Zero-touch: the agent under test is a black box. The simulator only needs the
agent's registered agent_name; it never reads or modifies the target project's code,
.env, or model config.
How it works
- Reads
<your-repo>/.agent-sim/config.yaml(LiveKit creds +agent_name+ simulator voice). - Creates a fresh room
lk-sim-<run-id>and dispatches the agent viaRoomAgentDispatch. - Joins as participant
lk-sim-caller, bridges audio with a Gemini Live session (gemini-3.1-flash-live-preview) playing the scenario persona. - Observes everything from inside the room:
lk.transcriptiontext streams, custom data topics (when configured), audio timing, interruptions, silences. - Writes
reports/<run-id>/—events.jsonl,timeline.md,summary.json,meta.json— and mirrors toruns.sqlite. - Optional LLM judge (
gemini-2.5-flash) scores the transcript + tool spans against the scenario's PassCriteria.
Quick start
# In the repo you want to test (agent worker must be running; set `agent_name` in config):
uv run --directory /path/to/livekit-agent-simulator lk-sim init
# → scaffolds .agent-sim/ (gitignored) — fill in config.yaml
uv run --directory /path/to/livekit-agent-simulator lk-sim run smoke-hello
uv run --directory /path/to/livekit-agent-simulator lk-sim report <run-id>
Cursor MCP config
{
"mcpServers": {
"livekit-agent-simulator": {
"command": "uv",
"args": ["run", "--directory", "/abs/path/livekit-agent-simulator", "livekit-agent-simulator-mcp"]
}
}
}
MCP tools
| Tool | Purpose |
|---|---|
init_project |
Scaffold .agent-sim/ + add to .gitignore |
list_scenarios |
Glob scenarios/*.jsonl |
validate_scenario |
Schema + lint |
run_scenario |
Run a simulation, returns run_id |
get_run_status |
running / done / failed + turn count |
get_run_log |
Read events.jsonl with kind/turn/source/time filters |
get_run_report |
Summary + judge verdict + suspicious turns |
compare_runs |
Diff two runs |
list_runs |
Run history from SQLite |
Docs
- AGENTS.md — rules for AI agents (research loop, package boundary)
- docs/smoke-test.md — first end-to-end run
- docs/portability.md — consumer-specific dispatch / observe setup
- docs/plugins.md — verify plugins + Python API
CI / Release
| Workflow | Trigger | What it does |
|---|---|---|
| CI | PR / push → master |
pytest (Python 3.10 + 3.12), lk-sim --help, uv build |
| Release | tag v* |
test → build → GitHub Release (wheel + sdist); PyPI if PYPI_API_TOKEN secret is set |
Local check:
uv sync --extra dev
uv run pytest -q
uv build
Release:
git tag v0.1.0
git push origin v0.1.0
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。