The Llama Logger MCP (Model Context Protocol) Server brings the power of AI directly to your error logs. Seamlessly integrate Llama Logger with Claude, Cursor, VS Code, and other AI-powered development tools to diagnose issues faster than ever before.
Traditional debugging workflows require you to:
With Llama Logger MCP, your AI assistant queries your logs directly.
Ask questions like:
Your AI handles the rest.
Add the following to your Claude Desktop configuration file:
Windows: %APPDATA%\Claude\claude_desktop_config.json
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"llamalogger": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://intake.llamalogger.com/api/mcp"],
"env": {
"API_KEY": "your-api-key-here"
}
}
}
}
Restart Claude Desktop after saving.
Add to your Claude Code settings (~/.claude/settings.json):
{
"mcpServers": {
"llamalogger": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://intake.llamalogger.com/api/mcp"],
"env": {
"API_KEY": "your-api-key-here"
}
}
}
}
Add to your Cursor MCP settings (.cursor/mcp.json in your project or global config):
{
"mcpServers": {
"llamalogger": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://intake.llamalogger.com/api/mcp"],
"env": {
"API_KEY": "your-api-key-here"
}
}
}
}
| Tool | Description |
|---|---|
search_logs |
Search and filter log entries with full-text search and pagination |
get_log_entry |
Get complete details of a specific log entry |
get_log_entry_history |
View all occurrences of a specific error signature |
get_project_summary |
Get project statistics, top exceptions, and activity trends |
star_entry |
Mark an entry for follow-up |
dismiss_entry |
Hide an entry from active view |
restore_entry |
Clear star or dismiss status |
add_comment |
Add investigation notes to an entry |
create_ignore_rule |
Auto-dismiss future matching errors |
list_ignore_rules |
View all ignore rules |
delete_ignore_rule |
Remove an ignore rule |
Once configured, try these prompts with your AI assistant:
"Search for any errors in the last 24 hours"
"Show me the full details and stack trace for log entry [ID]"
"What's the history of this NullReferenceException? When did it first appear?"
"Give me a summary of my project - what are the top exceptions?"
"How many errors occurred in the last 7 days compared to the last 30?"
"Star this error for follow-up"
"Add a comment to this entry: 'Investigating - may be related to the auth refactor'"
"Create an ignore rule for TaskCanceledException - these are expected during shutdown"
"Dismiss all the OperationCanceledException errors"
The search_logs tool supports powerful filtering:
| Parameter | Type | Description |
|---|---|---|
searchText |
string | Full-text search across all fields |
status |
string | Normal, Starred, or Dismissed |
loggingLevel |
string | Diagnostic, Info, Warning, Error, or Required |
exceptionType |
string | Exact exception type name |
fromDate |
ISO 8601 | Start of date range |
toDate |
ISO 8601 | End of date range |
customDataName |
string | Filter by custom data field name |
customDataValue |
string | Filter by custom data field value |
pageSize |
integer | Results per page (1-100, default 20) |
pageNumber |
integer | Page number (default 1) |
npx is available in your PATHLlama Logger MCP Server - Because your AI should know what's breaking.