官方说明7 个来源MCP 服务8 天前

ejcho623/agent-breadcrumbs

📇 ☁️ 🏠 - Unified work logging and observability across AI agents, with config-first schemas and pluggable…

配置模板（请按你的客户端调整）

claude mcp add agent-breadcrumbs -- npx -y agent-breadcrumbs

这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。

★ 数取值: 4 ★ · ejcho623/agent-breadcrumbs · 取自 GitHub 搜索 API · （2026-10-16 20:00:20 核对）
来源明细: 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
收录与活跃: 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成: 综合分 703 · 4 ★ · 7 个来源 · mcp

常见问题（答案都来自我们的记录）

怎么安装？

我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。

它适合谁 / 用来做什么？

我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。

谁维护它、还在更新吗？

仓库 ejcho623/agent-breadcrumbs；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。

第三方质量标记

Agent Breadcrumbs 🍞

以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →

Lightweight logging & observability for agent work across clients (Codex, Claude, Cursor, ChatGPT, OpenClaw, and others).
https://github.com/user-attachments/assets/3eac31a8-107c-4a82-a14c-dcfa500dd1a9
What You Get
- One MCP tool (log_work) that aggregates work done across different agents for single or multiple users.
- Define your own logging structure with custom schemas (or use built-in profiles) once, and the MCP schema
will guide clients to log with correct payloads.
- This lets teams standardize logging once, then route data wherever they need it.
- Multiple options for output sinks:
- local JSONL
- webhook
- Postgres
- Starter schema profiles for common use cases:
- agent insights
- delivery tracking
- audit trail
- knowledge capture
- Simple dashboard app to view logged work.
Repository Layout
- MCP server package (published): packages/mcp
- Dashboard app (repo-local, not published): apps/dashboard
Quick Start (MCP)
Install and run with defaults:
Use with an explicit config file:
Codex config example (~/.codex/config.toml):
--config is optional. If omitted, server defaults are used:
Claude Desktop (claude_desktop_config.json):
OpenClaw:
After you install the MCP server make sure to use mcporter so the server can be called through the CLI.
Then add a system prompt to the channel you're using.
For cron-driven workflows, instruct agents to call log_work on each scheduled run
for regular time-based logging.
General example global instruction/system prompt for clients:
For full MCP server setup, config, and sink details, see packages/mcp/README.md.
Quick Start (Repo)
Run MCP server locally with a sample config:
Run dashboard locally:
MCP Config Model
Top-level config file is JSON and supports:
- schema for fully custom log_record properties, or
- schema_profile for built-in profile files in packages/mcp/examples/schema_profiles
- user_name for server-side user identity injection into persisted records
- sink for destination settings (jsonl, webhook, postgres)
Do not set both schema and schema_profile together.
Default behavior when omitted:
- schema: built-in default (agent_id, timestamp, work_summary, additional)
- sink: jsonl
- output file: ~/.agent-breadcrumbs/logs.jsonl