add-integration

Register MCP servers by adding YAML entries to config/mcp_servers.yaml.

34|5|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/ebongard/renfield --skill add-integration-ebongard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-integration
Source: https://github.com/ebongard/renfield/tree/main/.claude/skills/add-integration
Command: npx skills add https://github.com/ebongard/renfield --skill add-integration-ebongard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about add-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add an MCP server to my application without writing code?

You can add MCP servers without code by defining them as YAML entries in config/mcp_servers.yaml. This declarative approach registers the server's tools automatically in the mcp.<name>.<tool> namespace.

Can I configure MCP servers using streamable_http, sse, and stdio transports?

Yes, MCP servers can be configured using streamable_http, sse, or stdio transports. This allows you to onboard both network services and local subprocess servers through your YAML configuration.

How do I control permissions and prompt filtering for MCP tools?

You control MCP tool permissions and prompt filtering by defining server-level and tool-level permission mappings alongside prompt_tools exposure directly within the YAML entry for each server.

Does MCP server configuration support background notification polling?

Yes, MCP server configuration supports background notification polling. You can enable proactive event polling by setting the optional notifications configuration and defining a refresh_interval in seconds.

What configuration fields are required to register a new MCP server?

Registering a new MCP server requires a name, transport type, and either a URL or command with arguments. Optional fields include prompt_tools, examples, permission mappings, refresh_interval, and notifications configuration.

How do I expose specific tools from an MCP server to prompts?

To expose specific MCP tools to prompts, you define the tool names in the optional prompt_tools list within the server's YAML entry. This filters which tools are available to the prompt system.