
LogBear
Local dev server logs for coding agents: errors, runs and diffs as read-only SQL.
- GitHub stars
- 2
- tools
- 5
- transport
- STDIO
- last updated
- Nov 10, 2026
Tools
5 toolsPublic tool metadata for what this MCP can expose to an agent.
logbear_schemaReturns the database schema so the agent can write queries against the recorded logs.
Returns the database schema so the agent can write queries against the recorded logs.
No parameter schema in public metadata yet.
logbear_queryRuns a read-only SQL query against the LogBear log database.
Runs a read-only SQL query against the LogBear log database.
No parameter schema in public metadata yet.
logbear_waitWaits for new log output or errors from the wrapped process.
Waits for new log output or errors from the wrapped process.
No parameter schema in public metadata yet.
logbear_diffCompares recorded runs or log output to show what changed.
Compares recorded runs or log output to show what changed.
No parameter schema in public metadata yet.
logbear_ackAcknowledges unread errors so they no longer appear in the unread-state warning.
Acknowledges unread errors so they no longer appear in the unread-state warning.
No parameter schema in public metadata yet.
Sponsors
Readme
The LogBear mascot
LogBear — local dev server logs for agents
Your coding agent can't see your dev server crash.
LogBear gives coding agents — Claude Code, Codex, pi and Hermes — your local dev server logs. It wraps a development process, records everything it emits, and tells your agent the moment something breaks.
logbear mix phx.server
That is the whole interface. Your terminal behaves as it did before — colours,
IEx.pry, Ctrl-C, resize — and everything the process prints is now queryable, diffable,
and visible to an agent that would otherwise have no idea it happened.
Contents
Details
- Repository
- github.com/teralabx/logbear
- Category
- Databases
- Package
logbear-mcp- Transport
- STDIO
- Registry
- MCP registry, active