EvoX 文件
  • 產品
  • 價格
  • 文件
  • 能力市集
返回 EvoMap
登入註冊
概览
实践案例
功能
配置
配置基础
项目工作规则技能管理插件与应用连接MCP 服务器
开发者
安全
管理
概览
实践案例
功能
配置
配置基础
项目工作规则技能管理插件与应用连接MCP 服务器
开发者
安全
管理
EvoX 文件/Product/MCP 服务器

MCP servers

Connect external tools to EvoX through MCP. A server can run as a local process or a remote service; follow its provider's instructions when choosing a transport.

Choose a connection type

Choose a server transport

Interactive illustration · This does not change your EvoX settings.

Launch a local tool process

Install the command and script locally first. This only illustrates how the fields fit together.

Command
node
Arguments
/absolute/path/to/server.mjs
Environment
SERVICE_TOKEN=YOUR_TOKEN
TransportWhat to prepare
stdioLocal executable, arguments, runtime dependencies, and environment variables
streamable-httpProvider-supplied MCP endpoint and any required headers

Use the provider’s MCP endpoint rather than its website homepage. A local command must be installed and runnable; supply the executable and required arguments rather than only a package name.

Add a local server

  1. Add an MCP server in extension management.
  2. Enter a recognizable name and select stdio.
  3. Enter the launch command and place arguments in their own field.
  4. Supply required environment variables, save, and test.
  5. Inspect the tools and try a read-only task.

For example, a provider-supplied local script can use node with the script's absolute path as an argument. Obtain the actual command from trusted installation instructions.

Add a remote server

  1. Select streamable-http.
  2. Enter the complete MCP endpoint supplied by the provider.
  3. Add headers as directed, one Header=value per line.
  4. Complete the service's authentication requirements, save, and test.
  5. Check what the connected account can access.

Example placeholders are not real credentials. Do not send existing account secrets to an unfamiliar endpoint.

Field reference

FieldPurpose
NameIdentify a connection; existing connections and guided Marketplace installs keep a fixed name
Command and argumentsLaunch a local tool process
URLAddress a remote MCP endpoint
Environment variablesSupply configuration required by the process
Request headersSupply authentication or extra information for a remote service
DisabledRetain configuration without loading the connection

An example variable is SERVICE_TOKEN=YOUR_TOKEN; use it only if that provider requires this variable. Never put a password in the connection name.

After connecting

Read tool names and descriptions to confirm the required capability exists. Start by reading one authorized item before creating, changing, or sending anything.

To maintain a server, open its edit action, check command or URL, environment, and authentication, then save. Existing names are fixed; do not rename a connection to change its identity. Enable Disabled to retain the configuration without loading it; clear Disabled and test its tools again to restore it.

Before removing a connection, confirm its name, preserve non-secret reconstruction details, and finish dependent tasks. Removal does not uninstall local dependencies, revoke remote credentials, or delete remote data. Revoke service-side authorization separately when ending access.

/mcp opens the unified status panel. Connected does not mean every tool is authorized or that the account can access every file.

Common problems

SymptomCheck in order
Local process will not startExecutable, argument paths, dependencies, environment
Remote endpoint is unreachableURL, network and proxy, server status
Authentication failsAccount, credentials, required authentication method
Expected tools are missingTool list, server version, account access
Reads work but writes failWrite-tool availability, account rights, and task authorization

Next: Network and background operation · Plugins and app connections

上一篇插件与应用连接下一篇联网搜索