What problem does it solve?
Provides a clear, no-code workflow to onboard external MCP servers into Renfield via declarative YAML so teams can expose new services and tools without touching application code or deployment artifacts.
Core Features & Use Cases
- YAML-driven registration: Register MCP servers by adding entries to config/mcp_servers.yaml so tools auto-appear as mcp.<server>.<tool>.
- Multiple transport support: Configure streamable_http, sse, or stdio transports for network or local subprocess servers.
- Access control & notifications: Define server- and tool-level permissions, prompt_tools filtering, refresh intervals, and optional notification polling for proactive events.
- Use Case: Onboard a calendar or home-automation MCP server to expose list_events and create_event tools with fine-grained permissions and background notification polling.
Quick Start
Add a new MCP server named calendar using streamable_http at http://localhost:9095/mcp with prompt_tools list_events and create_event and enable notifications with a 900 second poll interval.