# Local MCP Servers
**Local MCP Servers** run directly on your Karini platform infrastructure, providing tools and capabilities to your copilots and recipes.
### Local MCP Server Configuration
The Local MCP Servers Registry enables you to register MCP servers using any of the following methods:
1. [**Upload File**](#method-1-upload-file)
2. [**Manual Input**](#method-2-manual-input)
3. [**Trusted Agent**](#method-3-trusted-agent)
#### Prerequisites
Before registering an MCP server, ensure the following are available:
* A valid MCP server JSON configuration schema.
* A server endpoint URL or command-based execution configuration.
* Appropriate authentication credentials, if required.
#### Method 1: Upload File
**Upload File** method allows importing pre-defined JSON configuration schemas from your local file system. The system reads the JSON file, validates its structure against the MCP server configuration schema, and registers the server with the parsed configuration.
**Steps:**
* Open the **MCP Registry** interface.
* You'll see the **Local MCP Servers** tab (default view).
* Select **Add new +** in the top-right corner.
* In the Add New MCP Server, provide the **Server Name**.
* Populate the **Description** with relevant technical context (e.g., purpose, integrations, ownership/maintainer details).
* In the Configuration Schema section, switch to the **Upload File** tab.
* Upload the JSON configuration by clicking the upload area.
* The system performs an initial file-type validation (**.json** required).
* Click **Add Server** to submit the registration.
* The server is registered in the registry and initialized for use.
**JSON Schema Structure:**
```
{
"your-server-name": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-github"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "your-token-here"
}
}
}
```
#### Method 2: Manual Input
Manual Input provides a text area for direct JSON entry within the browser interface.
**Steps:**
* Access the **MCP Registry interface**.
* You'll see the **Local MCP Servers** tab (default view).
* Click **Add new +** in the top-right corner.
* In the Add New MCP Server, enter the **Server Name**.
* Provide a concise **Description** for the server.
* In the Configuration Schema section, select the **Manual Input** tab.
* Enter or paste the JSON configuration into the embedded code editor.
* Resolve any syntax issues flagged in red.
* Click **Add Server**.
* The server is registered and initialized within the registry.
**JSON Schema Structure:**
```
{
"server-name": {
"command": "uvx",
"args": ["package-name@latest"],
"env": {
"API_KEY": "your-key",
"REGION": "us-east-1"
}
}
}
```
#### Method 3: Trusted Agent
Trusted agents are pre-configured MCP servers.
**Steps:**
* Navigate to **MCP Registry interface.**
* You'll see the **Local MCP Servers** tab (default view).
* Click **Add new +** button in the top-right corner
* In the modal dialog, select **Trusted Agent** tab.
* Browse the list of available trusted MCP servers.
* Locate the desired MCP server from the list.
* Click the **'+'** button in the **Add MCP** column for that specific server.
* A pop-up will appear with **pre-filled server name and description.**
* Review or modify the server name and description if needed.
* Click **Add Server** button at the bottom of the pop-up
* The server will be registered and appear in your MCP Registry list.
### MCP Registry Server Management
Once registered, each MCP server appears in the MCP Registry with the following controls and indicators:
#### Server Details
* **Server Name:** Displays the unique MCP server identifier (e.g., `karini-sap-odata-mcp`).
* **Configuration Preview:** Shows a snapshot of the execution command and arguments.
* **Enable / Disable Toggle**
* Enabled servers are available for use in tools and prompt workflows (including Prompt Playground).
* Disabled servers remain listed but are unavailable for selection in agent prompts.
#### Testing a Server Connection
Verify your server is configured correctly and working.
* Enter an MCP request and click **Send request.**
* View execution output in the **Response** panel.
* Use **Reset** to clear inputs.
#### Usage Indicators
* Displays references to linked assets such as **Recipes** and **Prompts**.
#### Administrative Actions
You can click the three dots (⋮) on a server card to see available options.
* **Tools** :See what capabilities a server provides.A modal opens showing:
* List of all available tools
* Tool names and descriptions
* Input parameters and schemas
* Return value types
* **Edit** : Update an existing server's configuration or credentials.
* **Remove Server** : Delete servers you no longer need.
* **View Config** : A modal opens showing
* Server name and key
* Full JSON configuration
* Environment variables (masked with \*\*\*\*\*\*\*)
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://karini-ai.gitbook.io/karini-ai-documentation/mcp/local-mcp-servers.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.