Coding agent
Your logs, inside your coding agent.
Libra Logs is an MCP server. Connect it once and Claude Code, Cursor, Codex or any MCP agent can ask which customers are failing and why, then read the log lines itself.
Questions you can ask
- What's broken for Northwind?
- Which customers need attention today?
- Show me the log lines behind Globex's problem.
- Search our logs for hubspot rejections in the last hour.
- Is Initech still hitting invoice timeouts?
Customer names are fictional examples.
> what's broken for Northwind?
● libra-logs · whats_broken
One open problem. HubSpot rejects Northwind's contact updates because software_used is read-only on their side.
It started Tuesday and affects 3 of their 8 people. Want me to trace where we write that field?
Connect in one paste.
Copy a setup prompt with a fresh key inside it and paste it into your agent. It adds Libra Logs as an MCP server in your user config, never a file your repo could commit, then checks the connection.
A read-only key
The prompt carries a fresh read-only key, so your agent can read customers, problems and logs. Revoke it anytime in Settings, under API keys.
Connect your coding agent
Sign in and copy one prompt for Claude Code, Cursor, Codex or any MCP agent, with your read-only key already inside it.
Or run it yourself: npx libra-logs mcp add
Ask your agent what's broken.
Sign in, copy the prompt, and your next question about a customer gets answered from their logs.