33a29d0946
#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
43 lines
1.1 KiB
Markdown
43 lines
1.1 KiB
Markdown
---
|
|
task_number: 109
|
|
title: Trinity Core MCP Logging in Trinity Console
|
|
status: Complete
|
|
priority: P2-Medium
|
|
is_blocker: false
|
|
owner: Michael
|
|
tags:
|
|
- trinity-core
|
|
- trinity-console
|
|
- logging
|
|
- infrastructure
|
|
estimated_hours: 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 ✅
|