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

Set up MCP bridge for Qwen3 via Ollama #1067

New Issue
Closed
opened 2026-03-23 12:52:49 +00:00 by perplexity · 0 comments
perplexity commented 2026-03-23 12:52:49 +00:00
Collaborator
Copy Link

Parent: #1063
Related: #982 (session crystallization tech stack)

Objective

Establish MCP (Model Context Protocol) integration so Qwen3-14B running in Ollama can call Timmy's MCP tools (Gitea, file system, shell, etc.).

Options (evaluate in order)

  1. Qwen-Agent native MCP — pip install qwen-agent[mcp] — first-party support from Qwen team
  2. ollmcp — Ollama-MCP bridge
  3. mcphost — Generic MCP host that works with Ollama
  4. ollama-mcp-bridge — Purpose-built bridge

Steps

  1. Evaluate each bridge option for stability and feature completeness
  2. Install and configure the selected bridge
  3. Register Timmy's MCP tools (Gitea API, file operations, shell execution)
  4. Test tool calling end-to-end: prompt → model → MCP tool → result → model response
  5. Document the setup in docs/mcp-setup.md

Acceptance Criteria

  • Qwen3-14B can invoke MCP tools via structured JSON tool calls
  • Round-trip latency (prompt → tool call → response) under 5 seconds for simple tools
  • At least Gitea list/create issue tools working via MCP

Notes

Qwen3 models are explicitly listed among recommended Ollama models for MCP/tool use. The 32K context window is sufficient for most agent loops with tool response injection.

Parent: #1063 Related: #982 (session crystallization tech stack) ## Objective Establish MCP (Model Context Protocol) integration so Qwen3-14B running in Ollama can call Timmy's MCP tools (Gitea, file system, shell, etc.). ## Options (evaluate in order) 1. **Qwen-Agent native MCP** — `pip install qwen-agent[mcp]` — first-party support from Qwen team 2. **ollmcp** — Ollama-MCP bridge 3. **mcphost** — Generic MCP host that works with Ollama 4. **ollama-mcp-bridge** — Purpose-built bridge ## Steps 1. Evaluate each bridge option for stability and feature completeness 2. Install and configure the selected bridge 3. Register Timmy's MCP tools (Gitea API, file operations, shell execution) 4. Test tool calling end-to-end: prompt → model → MCP tool → result → model response 5. Document the setup in `docs/mcp-setup.md` ## Acceptance Criteria - Qwen3-14B can invoke MCP tools via structured JSON tool calls - Round-trip latency (prompt → tool call → response) under 5 seconds for simple tools - At least Gitea list/create issue tools working via MCP ## Notes Qwen3 models are explicitly listed among recommended Ollama models for MCP/tool use. The 32K context window is sufficient for most agent loops with tool response injection.
claude self-assigned this 2026-03-23 13:44:34 +00:00
claude added the harnessinferencep0-critical labels 2026-03-23 13:53:02 +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 harness inference p0-critical
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees claude
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1067
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?