SAG Wiki Docs

Tools & MCP

Choose built-in tools and external MCP servers per answer model.

Location and scope

Location: Settings → Q&A settings → Tool bindings. Select the answer model first. Each model keeps its own server bindings and enabled tools.

External server connection details can be reused by multiple models. Each model independently selects which servers and tools it may use.

Built-in SAG tools

Enable SAG (built-in MCP) without additional connection settings. Expand its tool list to enable or disable individual tools.

ToolPurpose
searchRetrieve source passages with SAG2 from a natural-language question; requires Jev
listFind files and directories within the registered scope
readRead source text at a known path and location
grepMatch keywords or patterns in file content
getTimeGet the current time
calculatePerform calculations

File tools respect the current query scope. Disabling the entire group prevents that model from retrieving the local knowledge base through these tools. Availability does not require a call on every turn. Calls are unlimited by default; setting a Q&A limit greater than 0 applies that shared limit to all tools.

Built-in SAG tools and external MCP bindings

Add an external server

Select Add server, or Add DeepWiki example for a preset connection. Fill in the dialog and select Add server. Headers, environment variables and confirmation controls are under Advanced settings. Test the example before use.

Connection settings in the Add MCP service dialog

FieldValue
Server nameA display name that distinguishes the server
Connection typeRemote HTTP or local command (stdio)
Server URLThe actual HTTP MCP endpoint
CommandThe stdio executable or command; use a full path when needed
ArgumentsOne argument per line
HeadersAn HTTP JSON object, such as authentication headers
Environment variablesA stdio JSON object with string values
Confirm before callingShow the tool name and arguments for user approval

Leave headers or environment variables blank to keep saved values. Enter {} to clear saved credentials. Retest and fetch the tool list after editing connection details.

Test, bind and select tools

  1. Fill the connection and select Test connection to retrieve tools.
  2. Enable its binding for the current model.
  3. Expand the tool list and enable only the tools you need.
  4. Select Save settings.
  5. After server changes, use Refresh tool list and review enabled tools.

A successful connection test does not guarantee correct model use of every tool. External tools may access networks or modify external resources; configure confirmation according to their capabilities.

Import JSON

The importer accepts mcpServers, servers or a single server object. This public example is supplied by the app:

{
  "mcpServers": {
    "DeepWiki": {
      "url": "https://mcp.deepwiki.com/mcp"
    }
  }
}

Select Import JSON, paste the configuration in the dialog and select Import configuration. Importing does not connect automatically. Rename duplicate server names. Streamable HTTP and stdio are supported; SSE, inputs and unresolved variable placeholders are not. Keep real configurations containing keys out of public documentation.

Remove a server

Remove server removes the connection and its model bindings when settings are saved. It does not uninstall the external program or delete data in the external system.

Connection dialogs

Add server and Import JSON open separate dialogs. After adding a server, test its connection and enable it for the current model. Removing a server asks for confirmation; the removal notice offers an undo action.

Add an MCP server

Import MCP configuration

On this page