MCP Support #5

Open
opened 2025-09-28 16:43:31 +02:00 by mpuchstein · 2 comments
Owner
  • Implement a new MCP provider that fetches context from an MCP server, prepends it to prompts, and integrates with Ollama.
  • Expose TCP/HTTP settings in config.toml and add “Enable MCP” toggle in the TUI.
- Implement a new MCP provider that fetches context from an MCP server, prepends it to prompts, and integrates with Ollama. - Expose TCP/HTTP settings in `config.toml` and add “Enable MCP” toggle in the TUI.
Owner

Relates to #4

Relates to #4
vikingowl added the enhancement label 2025-09-28 16:49:22 +02:00
Author
Owner

MCP integration

  • Use MCP’s dynamic capability discovery so the client can query connected servers for tools/resources/prompts and build a unified registry visible to the planner and executor.

  • Represent providers/models as discoverable resources or a “providers/list” tool, including metadata (capabilities, max tokens, cost class), so the planner can choose within strict boundaries.

  • Keep model credentials and routing logic on the client side; MCP servers expose tools, while the orchestrator decides which model invokes which tools at each step.

MCP integration - Use MCP’s dynamic capability discovery so the client can query connected servers for tools/resources/prompts and build a unified registry visible to the planner and executor. - Represent providers/models as discoverable resources or a “providers/list” tool, including metadata (capabilities, max tokens, cost class), so the planner can choose within strict boundaries. - Keep model credentials and routing logic on the client side; MCP servers expose tools, while the orchestrator decides which model invokes which tools at each step.
mpuchstein changed title from [feat] MCP Support to MCP Support 2025-09-28 17:11:45 +02:00
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Owlibou/owlen#5