MCP
Configure Model Context Protocol servers, refresh their tools, and share servers with your workspace.
Model Context Protocol (MCP) servers extend the agent with additional tools. Define local or remote servers in mcp.json, then use Settings to inspect their status and control workspace sharing.
Where to find it
Open Settings → MCP.
Server definitions live at:
~/.endos/mcp.jsonThe file supports both local stdio servers and remote MCP endpoints.
Controls
| Control | What it does |
|---|---|
| Add | Opens or creates mcp.json in Writer so you can edit server definitions. |
| Refresh | Reloads the server list and connection status. |
| Your servers | Shows each server's name, type (stdio or remote), and connection status. |
| Shared with everyone | Shares a server you own with the workspace. |
| Shared with you | Shows a read-only list of servers shared by other members. |
Configure mcp.json
The file must be valid JSON with a top-level mcpServers object. Each key is a server name that you choose; that name becomes part of the generated mcp_* tool names.
{ "mcpServers": { "local-server": { "command": "npx", "args": ["-y", "some-mcp-server-package"], "env": { "API_KEY": "..." }, "disabled": false }, "remote-server": { "url": "https://example.com/mcp", "headers": { "Authorization": "Bearer ..." }, "disabled": false } }}Field reference
| Field | Server type | Meaning |
|---|---|---|
command | stdio | Executable to spawn. Required for a local server. |
args | stdio | Optional list of command arguments. |
env | stdio | Optional environment variables for the server process. |
cwd | stdio | Optional working directory. |
url | remote | MCP endpoint URL. Required for a remote server. |
headers | remote | Optional HTTP headers, such as authorization headers. |
disabled | both | Set to true to keep the definition without connecting to the server. |
Each server must define either command for a stdio server or url for a remote server. An entry with neither field is invalid.
The format is compatible with MCP server entries used by Cursor and Claude Desktop.
Load tools after editing
After saving mcp.json, select Refresh in Settings → MCP, or ask the agent to refresh MCP tools. Newly connected capabilities then appear in the current conversation, typically with names beginning with mcp_*.
Connected servers make their tools available to the agent. Turning on Shared with everyone makes a server available beyond your private instance, using a sharing model similar to skills and app integrations.
Inside the desktop container, you can also inspect MCP through the endos-mcp command-line interface described in Native APIs and CLIs.