Activity

Problem

The deployment tool with action: get returns extremely large responses that can quickly fill up context. A simple deployment status check returned ~13.4k tokens.

What happened

coolify - deployment (action: "get", uuid: "xxx", lines: 20)
⚠ Large MCP response (~13.4k tokens), this can fill up context quickly

Even with lines: 20 parameter, the response was massive because:

1. The full deployment object is returned with all metadata
2. Build logs contain verbose output (Dockerfile with all ARGs repeated 3x, full composer package lists, npm output, etc.)
3. The logs field is a JSON-encoded string containing the entire build history

Suggested improvements

1. Smarter defaults - Return a summary by default, full logs only when explicitly requested
2. Better truncation - lines param should truncate more aggressively
3. Separate endpoints - get for status/summary, logs for full build output
4. Structured summary - Return key info (status, duration, commit, last few log lines) instead of everything

Example of what would be useful

{
  "status": "finished",
  "application_name": "devtrends", 
  "commit": "c93a685...",
  "commit_message": "feat: add DevTrends MCP...",
  "duration_seconds": 120,
  "recent_output": ["Container started", "Health check passed"]
}

Instead of 500+ lines of raw build logs.