firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity
Files
33a29d094621aa20567ecdd50e762bb028f27d21
firefrost-operations-manual/docs/tasks-index/task-109-mcp-logging.md
Claude 33a29d0946 task: Complete Tasks #109, #111, #112 
#109 MCP Logging — Fully operational. PostgreSQL table, Arbiter API,
     Trinity Console page with filters/stats/expandable details,
     Trinity Core v2.3.0 POSTs logs after every command.

#111 Trinity Core Web MCP — Completed by Chronicler #77.
     Claude.ai native connector working since Apr 11.

#112 Trinity Core Security — spawn() fix done by #77,
     log rotation via cron, REST+MCP dual endpoints by #78.

Chronicler #78 | firefrost-operations-manual
2026-04-11 11:56:24 +00:00

1.1 KiB
Raw Blame History

task_number, title, status, priority, is_blocker, owner, tags, estimated_hours
task_number title status priority is_blocker owner tags estimated_hours
109 Trinity Core MCP Logging in Trinity Console Complete P2-Medium false Michael
trinity-core
trinity-console
logging
infrastructure
4

Trinity Core MCP Logging

Add MCP command logging to Trinity Console. All commands executed through Trinity Core will be logged to PostgreSQL and viewable at /admin/mcp-logs with filtering by server, status, and date.

Why

  • Centralized audit trail for all remote commands
  • No Discord noise — silent logging
  • Searchable/filterable history
  • Consistent with Trinity Console architecture

Components

  1. mcp_logs PostgreSQL table
  2. Arbiter /api/internal/mcp/log endpoint
  3. Trinity Core updated to POST logs to Arbiter
  4. Trinity Console /admin/mcp-logs page with filters

Full Spec

See docs/tasks/task-109-mcp-logging/README.md for complete implementation details including SQL schema, API code, and UI template.

Prerequisites

  • Trinity Core deployed ✅
  • Arbiter running ✅
  • INTERNAL_API_TOKEN configured ✅
Reference in New Issue View Git Blame Copy Permalink