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
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
| Transport | What to prepare |
|---|---|
| stdio | Local executable, arguments, runtime dependencies, and environment variables |
| streamable-http | Provider-supplied MCP endpoint and any required headers |
A website homepage is usually not an MCP endpoint. A local command must also be installed and runnable; a package name alone may not be sufficient.
Add a local server
- Add an MCP server in extension management.
- Enter a recognizable name and select stdio.
- Enter the launch command and place arguments in their own field.
- Supply required environment variables, save, and test.
- Inspect the tools and try a read-only task.
For a provider-supplied local script, the command might be node with the script's absolute path as an argument. Obtain the actual command from trusted installation instructions.
Add a remote server
- Select streamable-http.
- Enter the complete MCP endpoint supplied by the provider.
- Add headers as directed, one
Header=valueper line. - Complete the service's authentication requirements, save, and test.
- 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
| Field | Purpose |
|---|---|
| Name | Identify a connection; existing connections and guided Marketplace installs keep a fixed name |
| Command and arguments | Launch a local tool process |
| URL | Address a remote MCP endpoint |
| Environment variables | Supply configuration required by the process |
| Request headers | Supply authentication or extra information for a remote service |
| Disabled | Retain 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.
Use /mcp to open the unified status panel. Connected does not mean every tool is authorized or that the account can access every file.
Common problems
| Symptom | Check in order |
|---|---|
| Local process will not start | Executable, argument paths, dependencies, environment |
| Remote endpoint is unreachable | URL, network and proxy, server status |
| Authentication fails | Account, credentials, required authentication method |
| Expected tools are missing | Tool list, server version, account access |
| Reads work but writes fail | Write-tool availability, account rights, and task authorization |