MCP Servers

Recommended setup

Use the desktop MCP setup assistant when adding a server.

Transport	Required fields	Optional fields
`stdio`	`command`	`args`, `env`, `cwd`
`http`	`url`	`headers`, auth-related fields supported by the server

MCP tools are deferred by server group. For example, a server named obsidian is loaded by the agent with:

load_tools(group="mcp:obsidian")

Command not found – use an absolute command path or install the package/binary first.
Missing env var – add required KEY=value entries in the server config.
HTTP auth failure – check headers or tokens and whether the server expects OAuth.
No tools appear – verify the server starts successfully and then reload MCP settings.