Built-in MCP server

The MCP server in OInt CLI is a built-in implementation of the Model Context Protocol over standard input/output (stdio) that you can use so an AI agent can work directly with the capabilities of the Open Integration Package.

Available tools

Tool	Purpose
get_services	List of available services (CLI commands) that correspond to OInt libraries
get_service_methods	List of methods for the selected service
get_method_parameters	Describes method parameters (types, default values, hints)
execute_method	Runs a method with a set of named parameters
get_variables	Returns the list of variables defined in the configuration file (see below)

Starting the server

Start the MCP server with oint mcp start and one or more parameters:

• --config (-c) — path to a JSON configuration file, or default to use the default configuration
• --log (-l) — path to a log file, if needed

Example start commands:

Bash

oint mcp start --config default
oint mcp start -c /home/user/oint-mcp.json -l /tmp/oint-mcp.log

CMD/Bat

oint mcp start --config default
oint mcp start -c C:\Users\user\oint-mcp.json -l C:\Temp\oint-mcp.log

PowerShell

oint mcp start --config default
oint mcp start -c "$env:USERPROFILE\oint-mcp.json" -l "$env:TEMP\oint-mcp.log"

You can get a template for your own configuration (the --config argument) with the separate command oint mcp config:

Bash

oint mcp config --empty true

CMD/Bat

oint mcp config --empty true

PowerShell

oint mcp config --empty true

When the command is run with --empty true, an empty JSON template is returned; with --empty false, explanatory example fields are added. Save the template by appending the standard --out <file path> option to the command or using shell redirection.

Configuration file

The configuration is a JSON file for various MCP server settings. Currently a single block is implemented — vars, which stores user-defined variable values. The agent can use these while running to substitute them for real data when calling the execute_method tool.

Example oint-mcp.json:

oint-mcp.json

{
  "vars": {
    "TelegramToken": "123456:ABC-DEF...",
    "BitrixWebhook": "https://example.bitrix24.ru/rest/1/xxxxx/"
  }
}

Starting the server with a configuration file:

Bash

oint mcp start -c /home/user/oint-mcp.json

CMD/Bat

oint mcp start -c C:\Users\user\oint-mcp.json

PowerShell

oint mcp start -c "$env:USERPROFILE\oint-mcp.json"

While running, the agent can call the get_variables tool to obtain the list of keys (names) of configured variables (without receiving their actual values). All of them are prefixed with @@ and can be supplied by the agent as values for OInt function parameters. When the MCP server receives such a value, it treats it as a variable key and replaces it with the real value from the configuration file. Secret data can therefore be used by the agent without passing it in plain text.

Connecting the server in AI agents

Below are examples of adding the OInt MCP server in various IDEs.

Cursor

In Cursor, MCP is configured in user or project settings (for example via the MCP settings in the UI or a file under .cursor).

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "default"]
    }
  }
}

For a configuration file that holds secrets, use an absolute path instead of default:

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "C:\\Users\\user\\oint-mcp.json", "-l", "C:\\Temp\\oint-mcp.log"]
    }
  }
}

See the Cursor MCP documentation for the current format and file location.

Kiro

Kiro uses:

• project-level: .kiro/settings/mcp.json
• user-level: ~/.kiro/settings/mcp.json

When both exist, they are merged; workspace settings take precedence.

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "default"]
    }
  }
}

For a configuration file that holds secrets, use an absolute path instead of default:

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "C:\\Users\\user\\oint-mcp.json", "-l", "C:\\Temp\\oint-mcp.log"]
    }
  }
}

Create or edit the config via the command palette (Kiro: Open workspace MCP config / Kiro: Open user MCP config). See Configuration in the Kiro documentation.

Cline

In Cline, servers are listed in JSON under the mcpServers key. File locations may change between extension versions; follow the current guide in the Cline documentation.

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "default"],
      "disabled": false
    }
  }
}

For a configuration file that holds secrets, use an absolute path instead of default:

{
  "mcpServers": {
    "oint-mcp": {
      "command": "oint",
      "args": ["mcp", "start", "-c", "C:\\Users\\user\\oint-mcp.json", "-l", "C:\\Temp\\oint-mcp.log"],
      "disabled": false
    }
  }
}

Server management (enable, restart) is available from the MCP panel in the Cline UI.

Diagnostics

If the client does not see the tools or fails on startup, run diagnostics in a terminal (command line):

1. Check that oint mcp start -c default runs without errors (the process should wait for input and not print messages to the console).
2. Check that the JSON in the configuration file is valid when using -c with a custom configuration.
3. Use logging (the -l option) and analyze the log after launch.