Tasks Added: - Task #109: MCP Logging in Trinity Console (full spec) - Task #110: Uptime Kuma monitor cleanup - Task #111: Claude Desktop MCP integration Consultations: - gemini-mcp-connector-2026-04-11.md - Full MCP protocol guidance - gemini-social-api-strategy-2026-04-10.md - Social sync strategy Key insights from Gemini: - Claude.ai web doesn't support custom MCP connectors yet - Use Claude Desktop + local wrapper script for now - Trinity Core REST API works as-is, no rewrite needed - Future: SSE support when Anthropic opens remote MCP Chronicler #76
1.1 KiB
1.1 KiB
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 | Planned | P2-Medium | false | Michael |
|
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
mcp_logsPostgreSQL table- Arbiter
/api/internal/mcp/logendpoint - Trinity Core updated to POST logs to Arbiter
- Trinity Console
/admin/mcp-logspage 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 ✅