Install and configure local Kobiton AI plugin

Install the local Kobiton AI plugin for Standalone (on-premises) deployments and for Cloud with a custom domain.

This guide does not apply to Claude Code or Claude Desktop.

Before you start

Make sure the Kobiton Portal version is at least 4.26.0S before continuing. Use the Help widget to verify the Portal version.

Retrieve your MCP server URL

Use the API base URL of your environment:

  1. Sign in to the Kobiton Portal.

  2. Select the Help icon, then choose API.

    Help widget open in the Kobiton Portal

  3. The API documentation home page opens. Copy the Base URL (Rest) value.

    The API documentation home page with Base URL visible

Add /mcp at the end of the retrieved API base URL. This will be the MCP server URL.

Examples:

Environment API base URL MCP server URL

Kobiton Cloud (default)

https://api.kobiton.com

https://api.kobiton.com/mcp

Cloud with custom domain

https://api-custom-domain.kobiton.com

https://api-custom-domain.kobiton.com/mcp

Standalone

https://custom-domain.kobiton.local:3000

https://custom-domain.kobiton.local:3000/mcp

If you are using the default Kobiton Cloud URL (https://api.kobiton.com/mcp), you can install the plugin from the online marketplace. Refer to guidance from the respective AI assistance tool to install and authenticate.

If you are using a custom environment, continue with this guide.

Download the Kobiton automate repository

Open a command-line tool on your machine:

  • macOS: Terminal

  • Windows: PowerShell or Command Prompt

If git is installed on your machine, clone the automate GitHub repository:

git clone https://github.com/kobiton/automate.git && cd automate

If you do not have git installed, download the repository as a .zip file, then extract it into the automate-main folder.

Edit MCP configuration

After retrieving the custom MCP URL, edit the following file in the automate or automate-main folder:

Platform MCP configuration file path

Copilot

.mcp.json

Gemini

gemini-extension.json

Codex

.codex/.mcp.json

For all files above, replace the default value of url with the custom MCP server URL.

Examples:

Default
{
  "mcpServers": {
    "kobiton": {
      "type": "http",
      "url": "https://api.kobiton.com/mcp",
      "headers": {
        "X-AI-Tool-Name": "Codex"
      }
    }
  }
}
Custom Cloud domain
{
  "mcpServers": {
    "kobiton": {
      "type": "http",
      "url": "https://api-custom-domain.kobiton.com/mcp",
      "headers": {
        "X-AI-Tool-Name": "Codex"
      }
    }
  }
}
Standalone
{
  "mcpServers": {
    "kobiton": {
      "type": "http",
      "url": "https://custom-domain.kobiton.local:3000/mcp",
      "headers": {
        "X-AI-Tool-Name": "Codex"
      }
    }
  }
}

Install local plugin

Run the install command for your platform in a command-line tool. Replace /path/to/automate with the actual path to the automate or automate-main folder.

Platform Command to install

Claude Code

claude plugin marketplace add /path/to/automate

claude plugin install automate@kobiton

Copilot

copilot plugin marketplace add /path/to/automate

copilot plugin install automate@kobiton

Gemini

gemini extensions install /path/to/automate

Codex

codex plugin marketplace add /path/to/automate

codex plugin add automate@kobiton

Verify MCP URL

After installing the plugin, verify that the MCP URL is configured correctly:

Platform Steps to verify

Copilot

copilot

/mcp

Verify the URL of kobiton

Gemini

gemini mcp list

Verify the URL of kobiton under Configured MCP servers

Codex

codex mcp list

Verify the URL of kobiton

Trust self-signed SSL certificate (Standalone only)

Import the certificate on each computer that runs the AI assistance tool.

Ask your IT administrator for the root CA certificate that issued the SSL end-entity certificate. It is typically named root.crt or ca.crt. Transfer the certificate file to the computer, then follow the steps for your operating system.

 

  • macOS

  • Windows

  • Linux

Open Keychain Access.

Open Finder, go to the location of the root CA certificate file, then drag the file into Keychain Access.

Double-click the newly added certificate file. In the dialog, select Always Trust from the dropdown list for the two fields:

  • Secure Sockets Layer (SSL)

  • X.509 Basic Policy

The trust option for the imported certificate in keychain access with the 2 options set as Always Trust

Close the dialog, then enter the administrator password for the computer to save the changes.

Double-click the certificate file, then select Install Certificate on the Certificate window.

The certificate information screen with an option to Install Cerficicate

On the next screen, select Local Machine. This requires administrator privileges.

The Certificate Import Wizard with the Store Location set to Local Machine

On the next screen, select Place all certificates in the following store, then select Browse.

The Certificate Store selector with the option Place all certificates in the following store selected

Select Trusted Root Certification Authorities, then select OK.

The Select Certificate Store screen with Trusted Root Certification Authorities selected

Select Next, then Finish. The root CA certificate is now in the computer’s trust store.

Trust the certificate using the steps for your distribution:

  • Debian-based: copy the certificate to /usr/local/share/ca-certificates (create the directory if it does not exist), then run update-ca-certificates as root.

  • Arch or Fedora: copy the certificate to /etc/ca-certificates/trust-source/anchors, then run update-ca-trust as root.

After importing the certificate, restart the AI assistance tool before authenticating with the MCP server.

Authenticate and use the plugin

Refer to the respective AI assistance tool guide to authenticate and use the plugin.