Skip to main content
Glama
ivan23kor

logpiper-mcp

by ivan23kor
README.md
# logpiper

[![npm]](https://www.npmjs.com/package/logpiper-mcp)

[npm]: https://img.shields.io/npm/v/logpiper-mcp.svg?style=flat-square

Logpiper is an MCP server and client for streaming terminal command logs with proactive error notifications

## Features

šŸš€ **Multi-Session Support**: Run multiple `logpiper` instances simultaneously across different terminals  
šŸ“Š **Real-time Streaming**: Only delivers new, unfetched logs via cursor-based streaming  
šŸ“¢ **Proactive Notifications**: Automatic alerts to Claude Code  

## Installation

Install npm package `logpiper-mcp` to access both components:

```bash
npm install -g logpiper-mcp
```

This provides:
- **CLI tool**: `logpiper` command for log collection
- **MCP server**: `logpiper-mcp` for IDE integration
- **Claude Code agent**: Install the monitoring agent with `logpiper --install-agent`

### Agent Installation

To install the Claude Code monitoring agent:

```bash
logpiper --install-agent
```

This will interactively guide you through installing the logpiper-monitor agent to your Claude Code agents directory.

### MCP Server Configuration

Add `logpiper` to your IDE configuration, e.g. `~/.claude/settings.json`:

```json
{
  "mcpServers": {
    "logpiper": {
      "command": "logpiper-mcp"
    }
  }
}
```

## Usage

### 1. Start monitoring any command by prefixing it with `logpiper`:

#### Testing and CI/CD
```bash
# Monitor test suites
logpiper npm test
logpiper npm run test:watch
logpiper npm run test:e2e

# Monitor build processes
logpiper npm run build
logpiper npm run build:prod
```

#### Docker and Container Monitoring
```bash
# Monitor Docker Compose services
logpiper docker-compose up
logpiper docker-compose logs -f backend

# Monitor individual containers
logpiper docker logs -f container_name
```

#### Database and Backend Services
```bash
# Monitor Python applications
logpiper python app.py
logpiper uvicorn main:app --reload

# Monitor Node.js servers
logpiper node server.js
logpiper nodemon app.js
```

### 3. MCP Tools Available

| Tool | Description | Usage |
|------|-------------|-------|
| `get_new_logs` | Get new logs since cursor position (streaming) | Real-time log monitoring |
| `list_sessions` | List all logging sessions with metadata | Session management |
| `search_logs` | Search through logs with query string | Error investigation |
| `get_logs_paginated` | Get logs with cursor-based pagination and automatic chunking | Large log file navigation |
| `cleanup_sessions` | Cleanup sessions: smart cleanup based on criteria or complete reset | Session management (mode: "smart" or "all") |

### Additional Features

šŸ”’ **Token Limiting**: MCP responses automatically limited to 25,000 tokens to prevent overwhelming Claude Code

## Contributing

1. Fork the repository
2. Create a feature branch
3. Add your improvements
4. Test with multiple command types
5. Submit a pull request

## License

MIT License - feel free to use and modify for your needs!

TDQS

B3.3/5.0

Scored across 5 tools

Disambiguation4/5

Most tools have clearly distinct roles, but get_new_logs and get_logs_paginated both retrieve logs and could be confused by an agent skimming descriptions. The streaming vs. pagination distinction is present but requires careful reading.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_, list_, search_, cleanup_), with no mixed conventions or vague verbs. The naming is predictable and easy to extrapolate.

Tool Count5/5

Five tools is a well-scoped size for a log management server, covering retrieval, search, session listing, and cleanup without unnecessary bloat or feeling thin.

Completeness3/5

The read and lifecycle side is reasonably covered with search, pagination, streaming, and cleanup, but there is no ingestion or write capability for logs/sessions. This is a notable gap if the server is meant to manage logs end-to-end.

Maintenance

ActivityInactive
ResponsivenessNo issues