MCP

Overview

The MCP Server Registry in Karini AI allows users to register, manage, and configure various MCP servers within the platform. This feature enables seamless integration of custom or pre-existing servers, offering full control over their configuration. Users can easily reference and manage these servers across different modules, enhancing system flexibility and interoperability.

The registry provides:

• Centralized visibility into server configurations

• Search and listing capabilities

• Operational controls such as enable/disable, test execution, edit, and removal

Karini’s MCP Registry supports the following types of MCP servers:

1. Local MCP Servers

2. Remote MCP Servers

Once the MCP servers are successfully registered, tested and enabled, the workflow proceeds as follows:

• The MCP servers become available as tools within Agent prompts in the Prompt Playground.

• These tools are selected and used during agent prompt testing to validate functionality and behavior.

• After successful validation, the agent prompts are published.

• The published prompts are then used to configure and build recipes and copilots, enabling end-to-end workflow execution across the platform.

• In Recipes, MCP server access is governed by authorization and recipe type. Users can authorize an MCP server when required and proceed with testing once access is granted. Key behaviors include:

  • In Chat Recipes, users can authorize the MCP server if it has not been previously authorized, and then test the recipe.

  • For Webhook Recipes, only service-based remote servers are supported.

  • If a user attempts to use a Remote MCP Server without authorization, the system displays a authorization pop-up to complete the access approval.

•