MCP Servers

Defines the configuration for MCP (Multiple Control Protocol) servers, enabling extended functionalities through server connections.

• mcp_servers: Defines one or more MCP servers as a named map of server definitions where each can have the following properties. These can be auto-loaded (see Autoload Settings) or you can load them using the /use_mcp command with the name in the config.
  • url: URL endpoint for the MCP server.
  • transport: (optional) The MCP protocol supports either http (modern) or legacy; default is auto which tries to pick the right one. For quick connectivity specify the transport.
  • bearer_auth_token: (optional) Token or API key required for authenticated access to the server that supports authentication.

Example

mcp_servers:
  weather:
    url: https://mcp.example.com/weather
    transport: http
    # only if the server requires authentication
    bearer_auth_token: secret_token