Updated on 2026-09-15 GMT+08:00

MCP

CodeArts Agent CLI connects to an MCP server through the Model Context Protocol (MCP) and uses the server's additional tools and resources to extend its capabilities.

Disclaimer

MCP servers are built, published, and maintained by third-party developers or organizations. CodeArts Agent does not review, verify, or endorse the code implementation, security, stability, data processing practices, or service quality of third-party MCP servers.

CodeArts Agent shall not be held liable for any risks arising from the use of third-party MCP servers, including but not limited to issues caused by defects in the MCP servers themselves, configuration errors, service anomalies, API changes, call failures, or the accuracy, completeness, and security of returned data.

Certain MCP servers may be inaccessible in specific countries or regions due to applicable laws and regulations, network constraints, policy adjustments by third-party services, or changes in service availability. CodeArts Agent has no control over these factors and cannot guarantee that all MCP servers will remain continuously available or fully functional across different regions or network environments.

Before using a third-party MCP server, users should independently assess its suitability and security risks, and ensure compliance with local laws and regulations as well as the terms of use and licensing requirements of the relevant third party.

For MCP servers involving sensitive operations on code, data, files, or account permissions, users are advised to fully understand their scope of permissions, data processing methods, and security policies before use, and to implement necessary security measures based on their specific business scenarios.

MCP Configuration Paths

You can configure the two types of MCP servers. Their corresponding configuration paths are shown in Table 1.

  • Local mode: Tool processes run directly on your computer. CodeArts Agent CLI starts them locally and communicates with them directly.
  • Remote mode: Tools run on another machine or a cloud server. CodeArts Agent CLI communicates with them over HTTP or WebSocket.
Table 1 MCP configuration paths

Type

Level

Scope of Application

Configuration Path and File

Local mode/Remote mode

Project

Current project

In the .codeartsdoer folder under your project's root directory, use codearts_cli.jsonc or codearts_cli.json as the configuration file.

User

All projects of the current user

In the current user's ~/.codeartsdoer directory, use codearts_cli.jsonc or codearts_cli.json as the configuration file.

The tilde (~) indicates the current user's home directory. In Windows, it is equivalent to C:\Users\Username\. In macOS, it is equivalent to /Users/Username/. In Linux, it is equivalent to /home/Username/.

Table 2 Parameters in the MCP configuration file for local mode

Parameter

Mandatory (Yes/No)

Parameter Type

Description

type

Yes

String

Fixed value: local

command

Yes

String array

Execution commands and parameters required to start the MCP service

environment

No

Object

Environment variables to inject when the MCP server is running

enabled

No

Boolean

Controls whether to enable the MCP server.

timeout

No

Number

Response timeout for obtaining MCP service tools, in milliseconds. Default: 100,000 ms

Table 3 Parameters in the MCP configuration file for remote mode

Parameter

Mandatory (Yes/No)

Parameter Type

Description

type

Yes

String

Fixed value: remote

url

Yes

String

Complete URL of the remote MCP server

headers

No

Object

Request headers

environment

No

Object

Environment variables to inject when the MCP server is running

oauth

No

Object

OAuth authentication configuration

enabled

No

Boolean

Controls whether to enable the MCP server.

timeout

No

Number

Response timeout for obtaining MCP service tools, in milliseconds. Default: 5,000 ms

MCP Server Configuration Example

The following example demonstrates how to configure a remote MCP server in Windows.

  1. In the %USERPROFILE%/.codeartsdoer/ directory, create a codearts_cli.jsonc file .
  2. In the created codearts_cli.jsonc file, configure the following content. Then, restart CodeArts Agent CLI.

    {
      "mcp": {
        // EdgeOne Pages Deploy MCP is a dedicated service that lets you quickly deploy web applications to EdgeOne Pages and generate public access links. This allows you to instantly preview and share AI-generated web content.
        "edgeone-pages": {
          "type": "remote",
          "url": "https://mcp-on-edge.edgeone.site/mcp-server",
          "enabled": true,
          "timeout": 45000,
          "headers": {
            // Optional API authentication header
            "Authorization": "Bearer edgeone_token_your_secret"
          }
        }
      }
    }

  3. Check whether the MCP configuration takes effect.

    /mcps

    If edgeone-pages shows Enabled, the MCP server is enabled.

    Figure 1 Enabled status

  4. Enter a prompt to invoke the MCP server and perform your task.

    Generate and release a snake game.

    AI invokes the MCP server and completes the creation of the snake game.

    Figure 2 MCP server invoked successfully