rai-mcp-add

Register MCP servers via guided conversation and generate validated YAML configs.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-mcp-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-mcp-add
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-mcp-add
Command: npx skills add https://github.com/humansys/raise --skill rai-mcp-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides a developer through MCP server registration without requiring CLI knowledge, enabling a conversational, intent-driven setup.

Core Features & Use Cases

  • Conversational collection of server intent and required details to set up an MCP server.
  • Catalog-assisted defaults via .raise/mcp/catalog.yaml for known servers and safe fallbacks when unknown.
  • Generates and validates the MCP config at .raise/mcp/{name}.yaml, then reports health and tools after installation.

Quick Start

Describe the MCP server you want to add and Rai will guide you through the registration steps.

Frequently Asked Questions about rai-mcp-add

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

FAQPage Schema
How do I register an MCP server without using the CLI?

You can register an MCP server conversationally by providing your intent and package details. The guided workflow collects required information, validates inputs, and generates the configuration file automatically.

What is a conversational MCP server registration workflow?

A conversational MCP server registration workflow collects your server intent, package details, and environment variables through interactive prompts. It adapts to your context using catalog-backed defaults for known servers and safe fallbacks for unknown ones.

Can I add an unknown MCP server that is not in the catalog?

Yes, you can add unknown MCP servers not in the catalog. The workflow uses interactive prompts to collect necessary details when catalog-assisted defaults are unavailable, ensuring safe fallbacks during registration.

Where does the MCP server config file get created during registration?

The MCP server config file is created at .raise/mcp/{name}.yaml. After generating and validating this configuration, the workflow reports server health and available tools to confirm successful installation.

Do I need environment variables to set up an MCP server?

Environment variables are collected during MCP server setup to ensure proper configuration. The conversational workflow prompts you for required environment variables alongside package details to validate and generate the config.

What happens after MCP server configuration is generated?

After MCP server configuration is generated and validated at .raise/mcp/{name}.yaml, the workflow reports server health and lists available tools. This confirms the installation succeeded and the server is operational.