Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[loop-generated] [refactor] Split timmy/mcp_bridge.py — 544 lines, MCP protocol integration #1394

New Issue
Closed
opened 2026-03-24 11:50:59 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 11:50:59 +00:00
Owner
Copy Link

Current State:

  • src/timmy/mcp_bridge.py is 544 lines handling MCP (Model Context Protocol) integration
  • Contains protocol implementation, server management, tool bridging, and message routing
  • Critical component for external tool integration and protocol compliance

Proposed Split:

src/timmy/mcp/
├── __init__.py          # Main MCP interface
├── protocol.py          # Core MCP protocol implementation
├── server.py            # MCP server management and lifecycle
├── tools.py             # Tool bridging and capability mapping
├── messages.py          # Message routing and serialization
└── client.py            # MCP client connection management

Benefits:

  • Better protocol version management
  • Easier to add new MCP features
  • Improved error handling and debugging
  • Better separation of client vs server concerns

Acceptance Criteria:

  • All MCP functionality preserved
  • Protocol compliance maintained
  • Tests pass
  • Tool integration still works
  • Each module under 150 lines
**Current State:** - `src/timmy/mcp_bridge.py` is 544 lines handling MCP (Model Context Protocol) integration - Contains protocol implementation, server management, tool bridging, and message routing - Critical component for external tool integration and protocol compliance **Proposed Split:** ``` src/timmy/mcp/ ├── __init__.py # Main MCP interface ├── protocol.py # Core MCP protocol implementation ├── server.py # MCP server management and lifecycle ├── tools.py # Tool bridging and capability mapping ├── messages.py # Message routing and serialization └── client.py # MCP client connection management ``` **Benefits:** - Better protocol version management - Easier to add new MCP features - Improved error handling and debugging - Better separation of client vs server concerns **Acceptance Criteria:** - [ ] All MCP functionality preserved - [ ] Protocol compliance maintained - [ ] Tests pass - [ ] Tool integration still works - [ ] Each module under 150 lines
Timmy commented 2026-03-24 11:55:56 +00:00
Author
Owner
Copy Link

Split src/timmy/mcp_bridge.py (544 lines) into focused modules:

Target structure:

  • src/timmy/mcp/bridge_core.py - Main bridge logic and connection handling
  • src/timmy/mcp/tool_registry.py - Tool registration and discovery
  • src/timmy/mcp/protocol_handler.py - Low-level MCP protocol operations

Instructions:

  1. Analyze the file to understand the logical separation points
  2. Split into 3 files maintaining all functionality
  3. Update imports in any files that reference mcp_bridge
  4. Ensure all tests pass: tox -e unit
  5. Verify no circular imports

Verification:

  • All existing functionality preserved
  • No test failures
  • Each new file <200 lines
  • Clear separation of concerns
Split src/timmy/mcp_bridge.py (544 lines) into focused modules: **Target structure:** - src/timmy/mcp/bridge_core.py - Main bridge logic and connection handling - src/timmy/mcp/tool_registry.py - Tool registration and discovery - src/timmy/mcp/protocol_handler.py - Low-level MCP protocol operations **Instructions:** 1. Analyze the file to understand the logical separation points 2. Split into 3 files maintaining all functionality 3. Update imports in any files that reference mcp_bridge 4. Ensure all tests pass: `tox -e unit` 5. Verify no circular imports **Verification:** - All existing functionality preserved - No test failures - Each new file <200 lines - Clear separation of concerns
kimi was assigned by Timmy 2026-03-24 11:55:56 +00:00
kimi was unassigned by Timmy 2026-03-24 19:33:26 +00:00
Timmy closed this issue 2026-03-24 21:54:16 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1394
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?